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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4FE3AE18.5050903@zytor.com>
Date:	Thu, 21 Jun 2012 16:28:24 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...64.org>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	"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/21/2012 02:58 AM, Borislav Petkov wrote:
> On Thu, Jun 21, 2012 at 10:24:35AM +0200, Peter Zijlstra wrote:
>> This thing is not installed on my machine, nor would I have know
>> to look for it. Nor does apt-cache search iucode_tool suggest any
>> package.
>>
>> IOW fail.
> 
> FWIW, if we agree that we need a userspace tool for massaging Intel's
> ucode, it should be in tools/ and it should be very easy to install even
> on a distro which doesn't distribute it.
> 
> Emphasis on the initial "if", of course.
> 
> I'd very much prefer tool-less ucode application.
> 

We're working on fixing that, however, we want to close on the early
ucode stuff and have it work first before we make any changes.

	-hpa

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