From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: [PATCH 0/3] Xen Microcode update driver for 2.6.38
Date: Thu, 11 Nov 2010 15:58:03 -0800 [thread overview]
Message-ID: <cover.1289519130.git.jeremy.fitzhardinge@citrix.com> (raw)
From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Hi all,
This series adds a new microcode driver for Xen. The Xen hypervisor
can deal with all the low-level details of doing a microcode update
(Intel vs AMD, doing all the physical CPUs present on the system,
current and future, etc), so all the driver has to do is make a
hypercall to upload the microcode into Xen.
This only works on a privileged domain, of course. But the Xen driver
also detects any time we're running paravirtualized under Xen to
prevent any attempts at a microcode update from a non-privileged
domain as well.
Thanks,
J
Jeremy Fitzhardinge (2):
xen: add CPU microcode update driver
xen/microcode: partially enable even for non-privileged kernels
Stephen Tweedie (1):
xen dom0: Add support for the platform_ops hypercall
arch/x86/include/asm/microcode.h | 9 ++
arch/x86/include/asm/xen/hypercall.h | 8 ++
arch/x86/kernel/Makefile | 1 +
arch/x86/kernel/microcode_core.c | 5 +-
arch/x86/kernel/microcode_xen.c | 201 ++++++++++++++++++++++++++++++
arch/x86/xen/Kconfig | 8 ++
include/xen/interface/platform.h | 222 ++++++++++++++++++++++++++++++++++
include/xen/interface/xen.h | 2 +
8 files changed, 455 insertions(+), 1 deletions(-)
create mode 100644 arch/x86/kernel/microcode_xen.c
create mode 100644 include/xen/interface/platform.h
--
1.7.2.3
next reply other threads:[~2010-11-11 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 23:58 Jeremy Fitzhardinge [this message]
2010-11-11 23:58 ` [PATCH 1/3] xen dom0: Add support for the platform_ops hypercall Jeremy Fitzhardinge
2010-11-15 15:48 ` Konrad Rzeszutek Wilk
2010-11-16 1:14 ` [Xen-devel] " Jeremy Fitzhardinge
2010-11-16 15:52 ` Konrad Rzeszutek Wilk
2010-11-11 23:58 ` [PATCH 2/3] xen: add CPU microcode update driver Jeremy Fitzhardinge
2010-11-15 15:59 ` Konrad Rzeszutek Wilk
2010-11-16 1:16 ` [Xen-devel] " Jeremy Fitzhardinge
2010-11-11 23:58 ` [PATCH 3/3] xen/microcode: partially enable even for non-privileged kernels Jeremy Fitzhardinge
2010-11-15 16:02 ` Konrad Rzeszutek Wilk
2010-11-16 1:17 ` [Xen-devel] " Jeremy Fitzhardinge
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=cover.1289519130.git.jeremy.fitzhardinge@citrix.com \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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.