linux-kernel - Re: [PATCH 2/2] x86, microcode: Make reload interface per system

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]

Message-ID: <4FE2585A.3000505@zytor.com>
Date:	Wed, 20 Jun 2012 16:10:18 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...64.org>,
	"Yu, Fenghua" <fenghua.yu@...el.com>, X86-ML <x86@...nel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: [PATCH 2/2] x86, microcode: Make reload interface per system

On 06/20/2012 04:08 PM, Henrique de Moraes Holschuh wrote:
> On Wed, 20 Jun 2012, Peter Zijlstra wrote:
>> On Wed, 2012-06-20 at 01:28 +0200, Borislav Petkov wrote:
>>> which makes me wonder whether we still need that OLD INTERFACE.
>>> Henrique, any thoughts here? 
>>
>> Yes I need it, I've no f'ing clue where to put the ucode image so that
>> the whole firmware mess can find it :-)
> 
> iucode_tool -K <name of intel microcode .dat/.bin file(s)> will do it
> for you :p
> 

I'm wondering about the new format... it seems to potentially make it
harder to do the proper retaining of compatible CPU microcodes.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/