xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	Xen Devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0
Date: Mon, 26 Sep 2011 11:17:59 -0700	[thread overview]
Message-ID: <cover.1317060617.git.jeremy.fitzhardinge@citrix.com> (raw)

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

Hi all,

I'm proposing this for the next merge window v3.2.

I originally posted this early this year, and it prompted a debate
about what the "proper" way that Linux should do microcode updates,
with the general concensus being "earlier", ideally in the bootloader
(or in the case of Xen, as the hypervisor boots before starting any
domains).  However, as far as I know there has been no progress along
those lines.

I would like to therefore merge this so that a Linux kernel booting as
dom0 under Xen can update the microcode in the same manner as a kernel
booting natively.  When we work out how boot-time microcode updates
can be done, then we'll look at modifying Xen accordingly.  In the
meantime, we should have a functional parity.

The only change to this code from the previous posting is some patch
restructuring so that regardless of how the platform.h ABI header gets
merged (since there are some other pending branches containing it), it
will be identical and cause no merge headaches.

>From original posting:

This series adds a new "Xen" microcode update type, in addition to
Intel and AMD.

The Xen hypervisor is responsible for performing the actual microcode
update (since only it knows what physical CPUs are in the system and
has sufficient privilege to access them), but it requires the dom0
kernel to provide the actual microcode update data.

Xen update mechanism is uniform independent of the CPU type, but the
driver must know where to find the data file, which depends on the CPU
type.  And since the update hypercall updates all CPUs, we only need
to execute it once on any CPU - but for simplicity it just runs it only
on (V)CPU 0.

Thanks,
	J

Jeremy Fitzhardinge (2):
  xen: add dom0_op hypercall
  xen: add CPU microcode update driver

Yu Ke (1):
  xen/acpi: Domain0 acpi parser related platform hypercall

 arch/ia64/include/asm/xen/interface.h |    1 +
 arch/x86/include/asm/microcode.h      |    9 +
 arch/x86/include/asm/xen/hypercall.h  |    8 +
 arch/x86/include/asm/xen/interface.h  |    1 +
 arch/x86/kernel/Makefile              |    1 +
 arch/x86/kernel/microcode_core.c      |    5 +-
 arch/x86/kernel/microcode_xen.c       |  198 ++++++++++++++++++++
 arch/x86/xen/Kconfig                  |    4 +
 include/xen/interface/platform.h      |  320 +++++++++++++++++++++++++++++++++
 include/xen/interface/xen.h           |    1 +
 10 files changed, 547 insertions(+), 1 deletions(-)
 create mode 100644 arch/x86/kernel/microcode_xen.c
 create mode 100644 include/xen/interface/platform.h

-- 
1.7.6.2

             reply	other threads:[~2011-09-26 18:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 18:17 Jeremy Fitzhardinge [this message]
2011-09-26 18:18 ` [PATCH 1/3] xen/acpi: Domain0 acpi parser related platform hypercall Jeremy Fitzhardinge
2011-09-26 18:18 ` [PATCH 2/3] xen: add dom0_op hypercall Jeremy Fitzhardinge
2011-09-26 18:18 ` [PATCH 3/3] xen: add CPU microcode update driver Jeremy Fitzhardinge
2011-10-12  0:40 ` [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Jeremy Fitzhardinge
2011-10-12 10:16   ` Borislav Petkov
2011-10-12 15:39     ` Jeremy Fitzhardinge
2011-10-12 18:18     ` H. Peter Anvin
2011-10-12 19:18       ` Jeremy Fitzhardinge
2011-10-12 19:45         ` Borislav Petkov
2011-10-12 20:40           ` Konrad Rzeszutek Wilk
2011-10-12 21:31             ` H. Peter Anvin
2011-10-12 21:40               ` Borislav Petkov
2011-10-12 22:49                 ` H. Peter Anvin
2011-10-12 23:40                   ` Jeremy Fitzhardinge
2011-10-12 23:55                     ` H. Peter Anvin
2011-10-13  0:00                       ` Jeremy Fitzhardinge
2011-10-13  0:03                         ` H. Peter Anvin
2011-10-13  7:00                           ` Borislav Petkov
2012-01-04  0:49                             ` Sven Köhler
2011-10-13  7:33                   ` Borislav Petkov
2011-10-13  9:57                     ` Borislav Petkov
2011-10-13 16:44                       ` H. Peter Anvin
2011-10-17 17:08                       ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-10-17 17:40                         ` H. Peter Anvin
2011-10-18  1:11                           ` Henrique de Moraes Holschuh
2011-10-18  8:56                           ` Christoph Egger
2011-10-18  9:35                             ` Borislav Petkov
2011-10-18  9:49                               ` Christoph Egger
     [not found]                             ` <m2n.s.1RGYF2-136675@chiark.greenend.org.uk>
2011-10-25 16:53                               ` Ian Jackson
2011-10-12 22:27           ` Jeremy Fitzhardinge
2011-10-12 22:29             ` H. Peter Anvin
2011-10-12 22:33               ` Jeremy Fitzhardinge
2011-10-12 22:34                 ` H. Peter Anvin
2011-10-12 22:38                 ` Borislav Petkov
2011-10-12 20:22         ` H. Peter Anvin
2011-10-12 22:34           ` Jeremy Fitzhardinge
2011-10-12 22:36             ` H. Peter Anvin
     [not found]         ` <m2n.s.1RE5NW-151309@chiark.greenend.org.uk>
2011-10-17 13:47           ` [Xen-devel] " Ian Jackson
2011-11-03 15:06 ` Ben Guthro
2011-11-03 16:47   ` [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.1317060617.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=tigran@aivazian.fsnet.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).