[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165909975658.253830.11461450313523332819.b4-ty@ellerman.id.au>
Date: Fri, 29 Jul 2022 23:02:36 +1000
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Christophe Leroy <christophe.leroy@...roup.eu>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>
Cc: linuxppc-dev@...ts.ozlabs.org,
Rashmica Gupta <rashmica.g@...il.com>,
Kajol Jain <kjain@...ux.ibm.com>,
Madhavan Srinivasan <maddy@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org,
Athira Rajeev <atrajeev@...ux.vnet.ibm.com>
Subject: Re: [PATCH v5 1/2] powerpc/perf: Use PVR rather than oprofile field to determine CPU version
On Thu, 7 Jul 2022 16:37:17 +0200, Christophe Leroy wrote:
> From: Rashmica Gupta <rashmica.g@...il.com>
>
> Currently the perf CPU backend drivers detect what CPU they're on using
> cur_cpu_spec->oprofile_cpu_type.
>
> Although that works, it's a bit crufty to be using oprofile related fields,
> especially seeing as oprofile is more or less unused these days.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/perf: Use PVR rather than oprofile field to determine CPU version
https://git.kernel.org/powerpc/c/ec3eb9d941a98f4c0dac263110729680a734279b
[2/2] powerpc: Remove remaining parts of oprofile
https://git.kernel.org/powerpc/c/62ccae78820b25a0ac64bb0f648388ec834fcb3c
cheers
Powered by blists - more mailing lists