Re: [PATCH v2 1/2] powerpc/perf: init pmu from core-book3s

2019-05-03 Thread Michael Ellerman
On Thu, 2019-04-04 at 11:54:49 UTC, Madhavan Srinivasan wrote: > Currenty pmu driver file for each ppc64 generation processor > has a __init call in itself. Refactor the code by moving the > __init call to core-books.c. This also clean's up compat mode > pmu driver registration. > > Suggested-by:

Re: [PATCH v2 1/2] powerpc/perf: init pmu from core-book3s

2019-04-29 Thread Madhavan Srinivasan
On 29/04/19 11:08 AM, Christophe Leroy wrote: Le 29/04/2019 à 04:52, Madhavan Srinivasan a écrit : Currenty pmu driver file for each ppc64 generation processor has a __init call in itself. Refactor the code by moving the __init call to core-books.c. This also clean's up compat mode pmu drive

Re: [PATCH v2 1/2] powerpc/perf: init pmu from core-book3s

2019-04-28 Thread Christophe Leroy
Le 29/04/2019 à 04:52, Madhavan Srinivasan a écrit : Currenty pmu driver file for each ppc64 generation processor has a __init call in itself. Refactor the code by moving the __init call to core-books.c. This also clean's up compat mode pmu driver registration. Can you explain the advantage

[PATCH v2 1/2] powerpc/perf: init pmu from core-book3s

2019-04-28 Thread Madhavan Srinivasan
Currenty pmu driver file for each ppc64 generation processor has a __init call in itself. Refactor the code by moving the __init call to core-books.c. This also clean's up compat mode pmu driver registration. Suggested-by: Michael Ellerman Signed-off-by: Madhavan Srinivasan --- Changelog v1: - A

[PATCH v2 1/2] powerpc/perf: init pmu from core-book3s

2019-04-04 Thread Madhavan Srinivasan
Currenty pmu driver file for each ppc64 generation processor has a __init call in itself. Refactor the code by moving the __init call to core-books.c. This also clean's up compat mode pmu driver registration. Suggested-by: Michael Ellerman Signed-off-by: Madhavan Srinivasan --- Changelog v1: - A