On Wed, Oct 28, 2015 at 12:47 AM, Will Deacon wrote:
>> + continue;
>> +
>
> Isn't this all racy against concurrent hotplug events? We're probably
> better off requesting the IRQs at PMU probe time, since we no longer have
> to worry about sharing the IRQ lines with
On Wed, Oct 21, 2015 at 03:56:02PM +0800, roy.qing...@gmail.com wrote:
> From: Li RongQing
>
> when there are 4 cpus, but only one is available to schedule, the warning
> will be generated when run the below command:
> # perf record -g -e cpu-clock -- find / -name "*.ko"
> CPU PMU:
On Wed, Oct 21, 2015 at 03:56:02PM +0800, roy.qing...@gmail.com wrote:
> From: Li RongQing
>
> when there are 4 cpus, but only one is available to schedule, the warning
> will be generated when run the below command:
> # perf record -g -e cpu-clock -- find / -name
On Wed, Oct 28, 2015 at 12:47 AM, Will Deacon wrote:
>> + continue;
>> +
>
> Isn't this all racy against concurrent hotplug events? We're probably
> better off requesting the IRQs at PMU probe time, since we no longer have
> to worry about sharing
From: Li RongQing
when there are 4 cpus, but only one is available to schedule, the warning
will be generated when run the below command:
# perf record -g -e cpu-clock -- find / -name "*.ko"
CPU PMU: unable to set irq affinity (irq=28, cpu=1)
CPU PMU: unable to set irq affinity
From: Li RongQing
when there are 4 cpus, but only one is available to schedule, the warning
will be generated when run the below command:
# perf record -g -e cpu-clock -- find / -name "*.ko"
CPU PMU: unable to set irq affinity (irq=28, cpu=1)
CPU PMU: unable
6 matches
Mail list logo