linux-kernel - Re: [patch 3/5] [PATCH 3/5] x86: Run Intel ucode-updates 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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 06 Aug 2008 13:31:18 -0700
From:	Max Krasnyansky <maxk@...lcomm.com>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Peter Oruba <peter.oruba@....com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 3/5] [PATCH 3/5] x86: Run Intel ucode-updates via workqueue.

Arjan van de Ven wrote:
> On Wed, 6 Aug 2008 17:21:20 +0200
> Peter Oruba <peter.oruba@....com> wrote:
> 
> [ no description or reason ]
> 
> Why is this?
> 
> I'm not very happy about this.. it means practically that this stuff
> *has* to run late. Probably later than we want to.
> (Like.. we may want to redo the microcode during resume.. which is
> not a schedulable context)

Dmitry and I tried to figure out how soon does it need to run.
Nobody had a strong argument why it must run synchronously in the 
hotplug path. Sure we want it as soon as possible and I'd say workqueue 
is soon enough.
Existing hotplug path does not guaranty any ordering and original 
microcode interface was driven from user-space. So clearly it was not 
considered very critical.

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/