From: Vince Weaver <vincent.weaver@maine.edu>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [perf] unchecked MSR access error: WRMSR to 0x3f1
Date: Thu, 19 Jun 2025 11:17:56 -0400 (EDT) [thread overview]
Message-ID: <52656281-ab73-baf7-0a80-ebcbe79dfca2@maine.edu> (raw)
In-Reply-To: <c04824b5-5697-1de5-0003-f2c5b73ed006@maine.edu>
On Wed, 18 Jun 2025, Vince Weaver wrote:
> On Wed, 18 Jun 2025, Liang, Kan wrote:
>
> > No, the error message doesn't say it. Just want to check if you have
> > extra information. Because the Topdown perf metrics is only supported on
> > p-core. I want to understand whether the code messes up with e-core.
>
> I can't easily tell from the fuzzer as it intentionally switches cores
> often. I guess I could patch the kernel to report CPU when the WRMSR
> error triggers.
I've patched the kernel to get rid of the warn_once() and added a printk
for smp_processor_id() (is that what I want to print?) In any case that
reports the warning is happening on CPU1 which is actually a P core, not
an atom core.
Vince Weaver
vincent.weaver@maine.edu
next prev parent reply other threads:[~2025-06-19 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:39 Vince Weaver
2025-06-17 15:50 ` Abhigyan ghosh
2025-06-17 19:47 ` Liang, Kan
2025-06-18 3:49 ` Vince Weaver
2025-06-18 11:02 ` Liang, Kan
2025-06-18 18:26 ` Vince Weaver
2025-06-19 15:17 ` Vince Weaver [this message]
2025-06-19 16:06 ` Liang, Kan
2025-06-19 20:10 ` Vince Weaver
2025-06-20 11:07 ` Liang, Kan
2025-06-20 16:12 ` Vince Weaver
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=52656281-ab73-baf7-0a80-ebcbe79dfca2@maine.edu \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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
all inboxes | Powered by JetHome®