linux-kernel - Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes

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: <4892738D.5040703@qualcomm.com>
Date:	Thu, 31 Jul 2008 19:23:09 -0700
From:	Max Krasnyansky <maxk@...lcomm.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Peter Oruba <peter.oruba@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes

Ingo Molnar wrote:
> * Dmitry Adamushko <dmitry.adamushko@...il.com> wrote:
> 
>> I've even suggested to consider doing microcode update somewhere 
>> earlier in start_secondary() (say, right before cpu_idle()). So it'd 
>> be done as ealry as possible + we don't mess up with cpu-hotplug 
>> events.
> 
> i have no problems with that approach in principle. Microcode updates 
> are special and black magic things anyway.
> 

I still think we should just do the update via schedule_work_on() and be 
done with it. Maybe in theory it should be done as early as possible but 
in practice hotplug handler -> workqueue will be soon enough, I think.

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/