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: <4FE2683E.4060707@zytor.com>
Date:	Wed, 20 Jun 2012 17:18:06 -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>,
	LKML <linux-kernel@...r.kernel.org>, x86 <x86@...nel.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>,
	"Yu, Fenghua" <fenghua.yu@...el.com>
Subject: Re: [PATCH] x86, microcode: Make reload interface per system

On 06/20/2012 05:06 PM, Henrique de Moraes Holschuh wrote:
> 
> No, because dd if=<whatever> of=/dev/cpu/microcode bs=1M means I have to
> add dd to the initramfs or to busybox, AND it will break the day the
> microcode data file gets bigger than 1M.  And it will be at best very
> annoying to have to special case each vendor to locate the correct
> microcode, etc.
>

No.

The whole point is you won't have to put ANYTHING in your initramfs,
period.  The early microcode blob will be all you need there.

So the only issue left is what to do when you want to update the
microcode in an already running system.

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