linux-kernel - Re: [PATCH v10 4/4] x86: Create a new synthetic cpu capability for machine check recovery

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]

Date:	Wed, 10 Feb 2016 12:06:03 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Lutomirski <luto@...nel.org>,
	Dan Williams <dan.j.williams@...el.com>, elliott@....com,
	Brian Gerst <brgerst@...il.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-nvdimm@...1.01.org, x86@...nel.org
Subject: Re: [PATCH v10 4/4] x86: Create a new synthetic cpu capability for
 machine check recovery

On Tue, Feb 09, 2016 at 03:38:57PM -0800, Luck, Tony wrote:
> We use the same model number for E5 and E7 series. E.g. 63 for Haswell.
> The model_id string seems to be the only way to tell ahead of time
> whether you will get a recoverable machine check or die when you
> touch uncorrected memory.

What about MSR_IA32_PLATFORM_ID or some other MSR or register, for
example?

I.e., isn't there some other, more reliable distinction between E5 and
E7 besides the model ID?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.