Oprofile Regression Caused by commite5d1367f17ba6a6fed5fd8b74e4d5720923e0c25 on PPC

[Eric B Munson]

This commit seems to have caused a regression with oprofile.  It is fairly easy
to trigger, simply run oprofile monitoring an event that will fire (something
frequent like CPU cycles) causes oprofile to fail saying that the PMU is in use.
If I disable CONFIG_CGROUP_PERF, everything goes back to working.  I suspect the
problem is that the PMU is being initialized without being reserved for perf.  I
am not yet sure of the right fix yet so if you have any suggestions I would
appreciate them.

Eric

Attachment: signature.asc
Description: Digital signature