From: Borislav Petkov <bp@suse.de>
To: x86-ml <x86@kernel.org>
Cc: Thomas Renninger <trenn@suse.de>, Kim Naru <kim.naru@amd.com>,
Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
lkml <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: [GIT PULL] AMD microcode loader fixes for 3.14
Date: Tue, 14 Jan 2014 12:50:06 +0100 [thread overview]
Message-ID: <20140114115006.GC29865@pd.tnic> (raw)
Hi guys,
please pull these microcode loader fixes which addresses early microcode
loading on AMD. The patches have been ready for a while now and I've
been running them here for weeks but was waiting for AMD to test them
too before I send out.
Also, I think it is finally time for the microcode loader to have its
own source tree directory, so the last patch does that. :-)
Please pull,
thanks.
---
The following changes since commit 7e22e91102c6b9df7c4ae2168910e19d2bb14cd6:
Linux 3.13-rc8 (2014-01-12 17:04:18 +0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/amd_ucode_for_3.14
for you to fetch changes up to bad5fa631fca5466401cd4a48e30cc1f1cb6101e:
x86, microcode: Move to a proper location (2014-01-13 20:00:12 +0100)
----------------------------------------------------------------
- AMD microcode early loading fixes
- some microcode loader source files reorganization
----------------------------------------------------------------
Borislav Petkov (4):
x86, ramdisk: Export relocated ramdisk VA
x86, microcode: Share native MSR accessing variants
x86, microcode, AMD: Fix early ucode loading
x86, microcode: Move to a proper location
arch/x86/Kconfig | 4 -
arch/x86/include/asm/microcode.h | 15 ++
arch/x86/include/asm/microcode_amd.h | 7 +-
arch/x86/include/asm/setup.h | 3 +-
arch/x86/kernel/Makefile | 9 -
arch/x86/kernel/cpu/Makefile | 1 +
arch/x86/kernel/cpu/microcode/Makefile | 7 +
.../{microcode_amd.c => cpu/microcode/amd.c} | 13 +-
.../microcode/amd_early.c} | 239 ++++++++++++++-------
.../{microcode_core.c => cpu/microcode/core.c} | 0
.../microcode/core_early.c} | 0
.../{microcode_intel.c => cpu/microcode/intel.c} | 0
.../microcode/intel_early.c} | 10 -
.../microcode/intel_lib.c} | 0
arch/x86/kernel/setup.c | 19 +-
15 files changed, 205 insertions(+), 122 deletions(-)
create mode 100644 arch/x86/kernel/cpu/microcode/Makefile
rename arch/x86/kernel/{microcode_amd.c => cpu/microcode/amd.c} (96%)
rename arch/x86/kernel/{microcode_amd_early.c => cpu/microcode/amd_early.c} (55%)
rename arch/x86/kernel/{microcode_core.c => cpu/microcode/core.c} (100%)
rename arch/x86/kernel/{microcode_core_early.c => cpu/microcode/core_early.c} (100%)
rename arch/x86/kernel/{microcode_intel.c => cpu/microcode/intel.c} (100%)
rename arch/x86/kernel/{microcode_intel_early.c => cpu/microcode/intel_early.c} (98%)
rename arch/x86/kernel/{microcode_intel_lib.c => cpu/microcode/intel_lib.c} (100%)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next reply other threads:[~2014-01-14 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 11:50 Borislav Petkov [this message]
2014-01-14 13:03 ` [GIT PULL] AMD microcode loader fixes for 3.14 Ingo Molnar
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=20140114115006.GC29865@pd.tnic \
--to=bp@suse.de \
--cc=aravind.gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=kim.naru@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
--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.