linux-kernel - Re: [patch 0/5] x86-microcode: run ucode update via workqueue

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: <489A0AFB.1030701@qualcomm.com>
Date:	Wed, 06 Aug 2008 13:35:07 -0700
From:	Max Krasnyansky <maxk@...lcomm.com>
To:	Dmitry Adamushko <dmitry.adamushko@...il.com>
CC:	Peter Oruba <peter.oruba@....com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/5] x86-microcode: run ucode update via workqueue

Dmitry Adamushko wrote:
> Hi Peter,
> 
>> Rebased Dmitry's patch set to x86-microcode and incorporated changes into AMD microcode patch loader. No issues with
>> cpu-hotplug anymore, tested on Intel as well as AMD.
> 
> btw., I still think we should consider running ucode-updates from the
> low-level arch code. But as it's perhaps a material for .28, there
> should be plenty of time. 

That'd be ok. Somehow I think it's not worth the effort though. If the 
machine was able to boot to the point that it can run user-space 
(request_firmware) with the old microcode it can probably sustain itself 
a bit longer while waiting for the workqueue thread to be scheduled.
You probably have more exciting things to do ;-)

The latest patches look ok btw.

Max

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