linux-kernel - Re: [PATCH] perf/x86: check ucode before disabling PEBS on SandyBridge

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2012 17:37:52 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Borislav Petkov <bp@...64.org>,
	Stephane Eranian <eranian@...gle.com>,
	linux-kernel@...r.kernel.org, andi@...stfloor.org, mingo@...e.hu,
	ming.m.lin@...el.com, "Yu, Fenghua" <fenghua.yu@...el.com>
Subject: Re: [PATCH] perf/x86: check ucode before disabling PEBS on
 SandyBridge

On Wed, 2012-06-13 at 07:00 -0700, H. Peter Anvin wrote:
> On 06/13/2012 01:38 AM, Peter Zijlstra wrote:
> > On Tue, 2012-06-12 at 13:58 -0700, H. Peter Anvin wrote:
> >>  even things like Nehalem + Westmere in the same system
> > 
> > Uhm,.. how well do you expect Linux to run on a franken-system like
> > that? I'm pretty sure perf will malfunction in such a setup.
> > 
> 
> perf might, but I have seen such frankensystems in the field and they
> work (although I haven't seen that particular combo, I have to admit.)

Thing is, if we boot on the wsm, perf could fault the system with
nonexistent MSR accesses, if we boot on the nhm worst is wrong numbers I
think.

I'm not really inclined to 'fix' this.. the best I'm willing to accept
is a patch that would detect this situation and simply disable all
hardware perf support for the platform.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/