linux-kernel - Re: [PATCH] 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: <4FDFF27C.5000205@zytor.com>
Date:	Mon, 18 Jun 2012 20:31:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Borislav Petkov <bp@...64.org>,
	LKML <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Dimitri Sivanich <sivanich@....com>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: [PATCH] x86, microcode: Make reload interface per system

On 06/18/2012 07:46 PM, Henrique de Moraes Holschuh wrote:
> 
> It is a pity this one is much harder to backport to 3.2 and 3.0.  I'd
> really like to have the new interface there.  But it looks good, and we
> will support the new /sys/devices/system/cpu/microcode/reload sysfs node
> in Debian for the benefit of anyone using a newer kernel than the
> distro's (which will be based on 3.2).
> 
> So, fwiw, you have my:
> Acked-by-unimportant-person: Henrique de Moraes Holschuh <hmh@....eng.br>
> 

I have to admit to being slightly questioning to the whole "sysfs
trigger, request_firmware" interface... it seems royally backwards to me
(it makes sense for the initial firmware load, I guess, but that is
better done early.)

Either way I don't have a hugely strong preference.

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