[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130812195816.GJ18018@pd.tnic>
Date: Mon, 12 Aug 2013 21:58:16 +0200
From: Borislav Petkov <bp@...en8.de>
To: x86-ml <x86@...nel.org>
Cc: Torsten Kaiser <just.for.lkml@...glemail.com>,
Johannes Hirte <johannes.hirte@....tu-ilmenau.de>,
lkml <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] AMD microcode fixes for 3.11
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(-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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/
Powered by blists - more mailing lists