lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f22dd6fb-48b7-99cf-3d7a-348e5792c8@maine.edu>
Date:   Mon, 11 Jul 2022 17:13:52 -0400 (EDT)
From:   Vince Weaver <vincent.weaver@...ne.edu>
To:     "Liang, Kan" <kan.liang@...ux.intel.com>
cc:     linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Jiri Olsa <jolsa@...nel.org>,
        Namhyung Kim <namhyung@...nel.org>,
        pawan.kumar.gupta@...ux.intel.com
Subject: Re: [perf] unchecked MSR access error: WRMSR to 0x689 in
 intel_pmu_lbr_restore

On Mon, 11 Jul 2022, Liang, Kan wrote:

> 
> 
> On 2022-07-08 12:13 p.m., Vince Weaver wrote:
> > [ 7763.384369] unchecked MSR access error: WRMSR to 0x689 (tried to write 0x1fffffff8101349e) at rIP: 0xffffffff810704a4 (native_write_msr+0x4/0x20)
> 
> The 0x689 is a valid LBR register, which is MSR_LASTBRANCH_9_FROM_IP.
> The issue should be caused by the known TSX bug, which is mentioned in
> the commit 9fc9ddd61e0 ("perf/x86/intel: Fix MSR_LAST_BRANCH_FROM_x bug
> when no TSX"). It looks like the TSX support has been deactivated,
> however the quirk in the commit isn't applied for some reason.
> 
> 
> To apply the quirk, perf relies on the boot CPU's flag and LBR format.
> 
> static inline bool lbr_from_signext_quirk_needed(void)
> {
> 	bool tsx_support = boot_cpu_has(X86_FEATURE_HLE) ||
> 			   boot_cpu_has(X86_FEATURE_RTM);
> 
> 	return !tsx_support && x86_pmu.lbr_has_tsx;
> }
> 
> Could you please share the value of the PERF_CAPABILITIES MSR	0x00000345
> of the machine?
> I'd like to double check whether the LBR fromat is correct. 0x5 is expected.

How would I do that?  Just something like:
# rdmsr 0x00000345
32c4

or is it more involved than that?

Vince Weaver
vincent.weaver@...ne.edu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ