From: Vince Weaver <vincent.weaver@maine.edu>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
Vince Weaver <vincent.weaver@maine.edu>,
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: Tue, 12 Jul 2022 15:39:56 -0400 (EDT) [thread overview]
Message-ID: <32ccdda1-63bf-746e-48fb-935fa58285b1@maine.edu> (raw)
In-Reply-To: <20220711221658.4gpkizopmftpnav6@guptapa-desk>
On Mon, 11 Jul 2022, Pawan Gupta wrote:
> Output of below would be helpful:
>
> # grep "rtm\|hle" /proc/cpuinfo
no results
> ARCH_CAP
> # rdmsr 0x10a
rdmsr: CPU 0 cannot read MSR 0x0000010a
> TSX_CTRL
> # rdmsr 0x122
rdmsr: CPU 0 cannot read MSR 0x00000122
> MCU_OPT_CTRL
> # rdmsr 0x123
0
> TSX_FORCE_ABORT
> # rdmsr 0x10f
rdmsr: CPU 0 cannot read MSR 0x0000010f
This is on a Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
Family model stepping: 6/60/3
Vince
next prev parent reply other threads:[~2022-07-12 19:48 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 [this message]
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
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=32ccdda1-63bf-746e-48fb-935fa58285b1@maine.edu \
--to=vincent.weaver@maine.edu \
--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=pawan.kumar.gupta@linux.intel.com \
--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®