From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>
Subject: Re: [PATCH] perf/x86/intel: use hexidecimal value for cpuid
Date: Thu, 9 Mar 2023 09:48:30 +0800 [thread overview]
Message-ID: <ZAk67tyBMde8k1C5@debian-scheme> (raw)
In-Reply-To: <20230308141619.GI2017917@hirez.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On 2023.03.08 15:16:19 +0100, Peter Zijlstra wrote:
> On Wed, Mar 08, 2023 at 11:15:01AM +0800, Zhenyu Wang wrote:
> > It's easier to use hexidecimal value instead of decimal for reading
> > and following with SDM doc, also align with other cpuid calls.
>
> *shrug*..
>
> > Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> > ---
> > arch/x86/events/intel/core.c | 2 +-
> > arch/x86/events/intel/lbr.c | 2 +-
> > arch/x86/events/intel/pt.c | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> > index 14f0a746257d..5af084198c8f 100644
> > --- a/arch/x86/events/intel/core.c
> > +++ b/arch/x86/events/intel/core.c
> > @@ -5903,7 +5903,7 @@ __init int intel_pmu_init(void)
> > * Check whether the Architectural PerfMon supports
> > * Branch Misses Retired hw_event or not.
> > */
> > - cpuid(10, &eax.full, &ebx.full, &fixed_mask, &edx.full);
> > + cpuid(0xA, &eax.full, &ebx.full, &fixed_mask, &edx.full);
> > if (eax.split.mask_length < ARCH_PERFMON_EVENTS_COUNT)
> > return -ENODEV;
>
> But now the data type names and the cpuid calls are no longer related.
oh, right, missed that. How about we change those too e.g union cpuid_0xa_eax?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-03-09 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 3:15 [PATCH] perf/x86/intel: use hexidecimal value for cpuid Zhenyu Wang
2023-03-08 14:16 ` Peter Zijlstra
2023-03-09 1:48 ` Zhenyu Wang [this message]
2023-03-12 13:26 ` [PATCH v2] perf/x86: " Zhenyu Wang
2023-03-22 5:37 ` [PATCH v3] " Zhenyu Wang
2023-03-24 13:33 ` Liang, Kan
2023-03-31 0:43 ` Zhenyu Wang
2023-03-31 13:26 ` Liang, Kan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAk67tyBMde8k1C5@debian-scheme \
--to=zhenyuw@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox