From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.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>
Subject: Re: [perf] unchecked MSR access error: WRMSR to 0x689 in intel_pmu_lbr_restore
Date: Thu, 14 Jul 2022 13:50:20 -0400 [thread overview]
Message-ID: <0f4f4f0b-7be1-97a8-feac-a3814a434a86@linux.intel.com> (raw)
In-Reply-To: <15f85765-ff2f-5d32-5991-06ef225706f0@maine.edu>
On 2022-07-14 12:12 p.m., Vince Weaver wrote:
> On Tue, 12 Jul 2022, Liang, Kan wrote:
>
>>
>> Could you please apply the below patch, reboot to the patched kernel and
>> share the dmesg log?
>
> here's the info with your patch applied:
>
> [ 0.000000] microcode: microcode updated early to revision 0x28, date = 2019-11-12
> ...
> [ 1.460296] NO HLE NO RTM. LBR has tsx 0
Thanks.
The issue should be introduced by the commit 1ac7fd8159a8
("perf/x86/intel/lbr: Support LBR format V7").
The quirk is invoked before the intel_pmu_lbr_init(), which set the
x86_pmu.lbr_has_tsx.
I will send out a patch to fix it shortly.
Thanks,
Kan
> [ 1.468217] Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
> [ 1.472292] ... version: 3
> [ 1.476275] ... bit width: 48
> [ 1.480275] ... generic registers: 4
> [ 1.484276] ... value mask: 0000ffffffffffff
> [ 1.488277] ... max period: 00007fffffffffff
> [ 1.492277] ... fixed-purpose events: 3
> [ 1.496271] ... event mask: 000000070000000f
>
> Vince
prev parent reply other threads:[~2022-07-14 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 21:14 [perf] odd fuzzer generated trace " Vince Weaver
2022-07-08 16:13 ` [perf] unchecked MSR access error: WRMSR to 0x689 " Vince Weaver
2022-07-11 15:25 ` Liang, Kan
2022-07-11 21:13 ` Vince Weaver
2022-07-12 0:11 ` Liang, Kan
2022-07-11 22:16 ` Pawan Gupta
2022-07-12 19:39 ` Vince Weaver
2022-07-12 20:48 ` Pawan Gupta
2022-07-12 21:26 ` Vince Weaver
2022-07-12 23:08 ` Liang, Kan
2022-07-14 16:12 ` Vince Weaver
2022-07-14 17:50 ` Liang, Kan [this message]
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=0f4f4f0b-7be1-97a8-feac-a3814a434a86@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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®