linux-kernel - Re: [PATCH 1/2] x86: Track minimum microcode revision globally

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] [day] [month] [year] [list]

Message-ID: <20120612210329.GD11413@one.firstfloor.org>
Date:	Tue, 12 Jun 2012 23:03:29 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
	Andi Kleen <andi@...stfloor.org>, x86@...nel.org,
	eranian@...gle.com, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/2] x86: Track minimum microcode revision globally

On Tue, Jun 12, 2012 at 10:59:56PM +0200, Borislav Petkov wrote:
> On Tue, Jun 12, 2012 at 01:52:14PM -0700, H. Peter Anvin wrote:
> > Different CPUs in a multisocket system may have different compatible
> > ucode versions.
> 
> Ah, so you need the different ucode for the different steppings of the
> cpus on the board, right? Assuming ucode versions are incremented per
> F:M:S tuple, of course, then you can have different compatible microcode
> versions.

I believe just for different models. Different models in a single system
may be possible, but are quite unsupported. The code doesn't
handle that, but I don't really worry about that.

> > Of course, I am not even sure if it makes any sense at all to compare
> > microcode versions without qualifying them with F:M:S.

It doesn't.

But I think this model handles 99.999% of all sane configs, don't
really want to complicate it more.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/