From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] x86/microcode changes for v3.7
Date: Mon, 1 Oct 2012 17:36:43 +0200 [thread overview]
Message-ID: <20121001153643.GA25751@gmail.com> (raw)
In-Reply-To: <20121001142439.GA24959@gmail.com>
* Ingo Molnar <mingo@kernel.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
prev parent reply other threads:[~2012-10-01 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 14:24 [GIT PULL] x86/microcode changes for v3.7 Ingo Molnar
2012-10-01 15:36 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121001153643.GA25751@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox