On Wed, 21 Jul 2021 01:48:28 -0400, Athira Rajeev wrote:
> Running perf fuzzer testsuite popped up below messages
> in the dmesg logs:
>
> "Can't find PMC that caused IRQ"
>
> This means a PMU exception happened, but none of the PMC's (Performance
> Monitor Counter) were found to be overflown. Pe
Excerpts from Athira Rajeev's message of November 20, 2021 12:36 am:
>
>
>> On 21-Jul-2021, at 11:18 AM, Athira Rajeev
>> wrote:
>>
>> Running perf fuzzer testsuite popped up below messages
>> in the dmesg logs:
>>
>> "Can't find PMC that caused IRQ"
>>
>> This means a PMU exception happened
> On 21-Jul-2021, at 11:18 AM, Athira Rajeev
> wrote:
>
> Running perf fuzzer testsuite popped up below messages
> in the dmesg logs:
>
> "Can't find PMC that caused IRQ"
>
> This means a PMU exception happened, but none of the PMC's (Performance
> Monitor Counter) were found to be overflow
Running perf fuzzer testsuite popped up below messages
in the dmesg logs:
"Can't find PMC that caused IRQ"
This means a PMU exception happened, but none of the PMC's (Performance
Monitor Counter) were found to be overflown. Perf interrupt handler checks
the PMC's to see which PMC has overflown an
