linux-kernel - Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode

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: <20080919060752.57542a50@infradead.org>
Date:	Fri, 19 Sep 2008 06:07:52 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Peter Oruba <peter.oruba@....com>
Cc:	cate@...ian.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	LKML <linux-kernel@...r.kernel.org>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>
Subject: Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to
 microcode_intel.c.

On Fri, 19 Sep 2008 13:59:39 +0200
Peter Oruba <peter.oruba@....com> wrote:

> Some additonal words regarding the current user space issues:
> 
> IMHO the most convenient way to update microcode is through the
> firmware loading interface instead of microcode_ctl. This reduces
> user-space responsibilities to loading the correct module at boot
> time and to place the microcode patch file at the right location via
> package installation. The problems mentioned in this thread would
> then probably disappear as well. What do you guys think?

while I absolutely don't disagree with what you say, breaking existing
userspace is not an option.
Yes I very much would like for microcode_ctl to die as well (in fact,
that was one of the reasons we had the microcode code use
request_firmware), but that doesn't mean we can just ditch
compatibility ;(
--
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/