From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] microcode fixes for tip/x86/urgent
Date: Mon, 10 Nov 2014 17:08:48 +0100 [thread overview]
Message-ID: <20141110160848.GA24585@gmail.com> (raw)
In-Reply-To: <20141110153137.GD4359@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> Hi guys,
>
> please queue those two fixes for early microcode loading on 32-bit for
> x86/urgent.
>
> Thanks.
>
> ---
> The following changes since commit e6023367d779060fddc9a52d1f474085b2b36298:
>
> x86, kaslr: Prevent .bss from overlaping initrd (2014-11-01 22:20:50 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/microcode_fixes_for_3.18
>
> for you to fetch changes up to c0a717f23dccdb6e3b03471bc846fdc636f2b353:
>
> x86, microcode, AMD: Fix ucode patch stashing on 32-bit (2014-11-10 13:50:55 +0100)
>
> ----------------------------------------------------------------
> Two fixes for early microcode loader on 32-bit:
>
> * access the dis_ucode_ldr chicken bit properly
> * fix patch stashing on AMD on 32-bit
>
> ----------------------------------------------------------------
> Borislav Petkov (2):
> x86, microcode: Fix accessing dis_ucode_ldr on 32-bit
> x86, microcode, AMD: Fix ucode patch stashing on 32-bit
>
> arch/x86/kernel/cpu/microcode/amd_early.c | 24 ++++++++++++++----------
> arch/x86/kernel/cpu/microcode/core_early.c | 2 +-
> 2 files changed, 15 insertions(+), 11 deletions(-)
Pulled, thanks Boris!
Ingo
prev parent reply other threads:[~2014-11-10 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 15:31 [GIT PULL] microcode fixes for tip/x86/urgent Borislav Petkov
2014-11-10 16:08 ` 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=20141110160848.GA24585@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.