linux-kernel - Re: [GIT PULL] x86/microcode changes for v3.7

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] [day] [month] [year] [list]

Date:	Mon, 1 Oct 2012 17:36:43 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Borislav Petkov <bp@...en8.de>
Subject: Re: [GIT PULL] x86/microcode changes for v3.7


* Ingo Molnar <mingo@...nel.org> wrote:

> Linus,
> 
> Please pull the latest x86-microcode-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-microcode-for-linus
> 
>    HEAD: bd13178169d5fd17da3221b55ba313270393649a Merge tag 'microcode_fix_3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp into x86/microcode
> 
> The biggest changes are to AMD microcode patching: add code 
> for caching all microcode patches which belong to the current 
> family on which we're running, in the kernel. We look up the 
> patch needed for each core from the cache at patch-application 
> time instead of holding a single patch per-system.

Something I forgot to mention: doing it this way is beneficial 
for suspend/resume and is generally the modern way of doing a 
self-sufficient in-kernel driver.

The natural next step will be to extend this approach to Intel 
CPUs (there's nothing inherently AMD specific about it) - that 
is still work in progress and was not ready for this merge 
window.

Just in case someone is wondering.

Thanks,

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