Even though we filter out bad performance counter names, it might still be the case where a PMC cannot be allocated due to system limits (eg perf_event_open returns -1 for any reason). In this case, the current implementation will drop the entire performance counter set.
Instead, filter out the failing PMC and warn the user. This was the behavior previously subject to a PR but this case slipped in, inherited.
The test for this fix is reflected in test/perf_counters_gtest.cpp under PerfCountersTest::NegativeTest.
Even though we filter out bad performance counter names, it might still be the case where a PMC cannot be allocated due to system limits (eg perf_event_open returns -1 for any reason). In this case, the current implementation will drop the entire performance counter set.
Instead, filter out the failing PMC and warn the user. This was the behavior previously subject to a PR but this case slipped in, inherited.
The test for this fix is reflected in test/perf_counters_gtest.cpp under PerfCountersTest::NegativeTest.