All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@alien8.de>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen Devel <Xen-devel@lists.xensource.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0
Date: Wed, 2 Feb 2011 10:48:48 -0200	[thread overview]
Message-ID: <20110202124848.GE9737@khazad-dum.debian.net> (raw)
In-Reply-To: <20110202095445.GA4761@liondog.tnic>

On Wed, 02 Feb 2011, Borislav Petkov wrote:
> Why would you need that? You can safely assume that the ucode patch
> level on all cores across the system are identical - I've yet to see a

No.  You can safely assume that the ucode patch level on all cores on a
package are identical, and that's it.  Mixing processors with different
processor flags (and thus potentially different microcode) is not uncommon.
If it boots, it *will* be done, especially later in the product cycle, when
specific spare parts are harder to come by.  Sometimes you can even mix
processors of different steppings.

> mixed silicon systems is a large pain in the ass and you're better off
> buying yourself a completely new system.

Well, I have some of them at work.

Mixed CPU steppings or processor flags happen when you expand the system
later to fill in processor packages (reasonably common), or when you replace
a CPU that is flaky (rare).  This sort of mixing of different processors is
really common on older Xeon systems, and most of them need OS-assisted
microcode updates to get the latest microcode available.

I am not arguing anything about the way Xen decided to go about implementing
the feature, but they got the requirement "must pass through all the
microcodes without removing any" right.  It exists.

> > However, even aside from that, it means exporting a pile of internal
> > details from microcode_amd and reusing them within microcode_xen.  And
> > it requires that it be done again for each vendor.
> 
> Why can't you load the appropriate, unmodified microcode_<vendor> module
> in dom0 and let it call the hypercall?

Or add a microcode_virtual passthrough device, for that matter.  Wouldn't
that be much cleaner and more palatable?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2011-02-02 12:48 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29  0:26 [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 Jeremy Fitzhardinge
     [not found] ` <cover.1296260656.git.jeremy.fitzhardinge@citrix.com>
2011-01-29  0:26   ` [PATCH 1/2] xen dom0: Add support for the platform_ops hypercall Jeremy Fitzhardinge
2011-01-29  0:26     ` Jeremy Fitzhardinge
2011-01-29  0:26   ` [PATCH 2/2] xen: add CPU microcode update driver Jeremy Fitzhardinge
2011-01-30 11:33 ` [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 Borislav Petkov
2011-01-31  2:34   ` Jeremy Fitzhardinge
2011-01-31  7:02     ` Borislav Petkov
2011-01-31  7:02       ` Borislav Petkov
2011-01-31 18:17       ` Jeremy Fitzhardinge
2011-01-31 18:17         ` Jeremy Fitzhardinge
2011-01-31 23:41         ` Borislav Petkov
2011-02-01  0:15           ` Jeremy Fitzhardinge
2011-02-01  0:15           ` Jeremy Fitzhardinge
2011-02-01  1:11             ` H. Peter Anvin
2011-02-01 22:52               ` Jeremy Fitzhardinge
2011-02-01 22:52                 ` Jeremy Fitzhardinge
2011-02-02 19:52                 ` H. Peter Anvin
2011-02-02 20:05                   ` Jeremy Fitzhardinge
2011-02-02 20:34                     ` Thomas Gleixner
2011-02-02 20:34                       ` Thomas Gleixner
2011-02-03  0:55                     ` Henrique de Moraes Holschuh
2011-02-03  0:58                       ` H. Peter Anvin
2011-02-03  7:47                       ` Borislav Petkov
2011-02-03 16:05                         ` Henrique de Moraes Holschuh
2011-02-03 16:05                           ` Henrique de Moraes Holschuh
2011-02-02 20:57                   ` Borislav Petkov
2011-02-02 20:57                     ` Borislav Petkov
2011-02-02 21:47                     ` H. Peter Anvin
2011-02-02 21:47                       ` H. Peter Anvin
2011-02-03 18:25                       ` Borislav Petkov
2011-02-03 18:33                         ` H. Peter Anvin
2011-02-03 18:33                           ` H. Peter Anvin
2011-02-01 11:00             ` Borislav Petkov
2011-02-01 23:12               ` Jeremy Fitzhardinge
2011-02-01 23:12                 ` Jeremy Fitzhardinge
2011-02-02  9:54                 ` Borislav Petkov
2011-02-02  9:54                   ` Borislav Petkov
2011-02-02 12:48                   ` Henrique de Moraes Holschuh
2011-02-02 12:48                   ` Henrique de Moraes Holschuh [this message]
2011-02-02 18:05                   ` Jeremy Fitzhardinge
2011-02-02 18:05                   ` Jeremy Fitzhardinge
2011-02-02 18:29                   ` Jeremy Fitzhardinge
2011-02-02 18:29                   ` Jeremy Fitzhardinge
2011-01-31  2:34   ` 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=20110202124848.GE9737@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=Xen-devel@lists.xensource.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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.