All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>,
	Torsten Kaiser <just.for.lkml@googlemail.com>,
	Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] AMD microcode fixes for 3.11
Date: Wed, 14 Aug 2013 12:17:41 +0200	[thread overview]
Message-ID: <20130814101741.GE10849@gmail.com> (raw)
In-Reply-To: <20130812195816.GJ18018@pd.tnic>


* Borislav Petkov <bp@alien8.de> wrote:

> Hi guys,
> 
> the tag message should explain it all so please pull.
> 
> Thanks.
> 
> The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:
> 
>   Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/amd_ucode_fixes
> 
> for you to fetch changes up to 84516098b58e05821780dc0b89abcee434b4dca5:
> 
>   x86, microcode, AMD: Fix early microcode loading (2013-08-12 18:32:45 +0200)
> 
> ----------------------------------------------------------------
> Those are basically two fixes which correct the AMD early ucode loader
> from accessing cpu_data too early, i.e. before smp_store_cpu_info()
> has copied the boot_cpu_data ontop and overwritten an already empty
> structure (which we shouldn't access that early in the first place
> anyway).
> 
> The second patch is kinda largish for that late in the game but it
> shouldn't be problematic because we're simply switching from using
> cpu_data to use the CPU family number directly and thus again, not use
> uninitialized cpu_data structure.
> 
> ----------------------------------------------------------------
> Torsten Kaiser (2):
>       x86, microcode, AMD: Make cpu_has_amd_erratum() use the correct struct cpuinfo_x86
>       x86, microcode, AMD: Fix early microcode loading
> 
>  arch/x86/include/asm/microcode_amd.h  |  2 +-
>  arch/x86/kernel/cpu/amd.c             | 20 +++++---------------
>  arch/x86/kernel/microcode_amd.c       | 27 +++++++++++++--------------
>  arch/x86/kernel/microcode_amd_early.c | 27 +++++++++++++--------------
>  4 files changed, 32 insertions(+), 44 deletions(-)

Pulled into x86/urgent, thanks Boris!

	Ingo

      reply	other threads:[~2013-08-14 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 19:58 [GIT PULL] AMD microcode fixes for 3.11 Borislav Petkov
2013-08-14 10:17 ` 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=20130814101741.GE10849@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=johannes.hirte@fem.tu-ilmenau.de \
    --cc=just.for.lkml@googlemail.com \
    --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.