All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Benjamin.Guthro@citrix.com, andrew.cooper3@citrix.com,
	Daniel Kiper <daniel.kiper@oracle.com>,
	stefan.bader@canonical.com, xen-devel <xen-devel@lists.xen.org>,
	david.vrabel@citrix.com
Subject: Re: Linux 3.11 and the future...
Date: Fri, 7 Jun 2013 13:03:52 -0400	[thread overview]
Message-ID: <20130607170352.GA3730@phenom.dumpdata.com> (raw)
In-Reply-To: <51B21BD802000078000DC42D@nat28.tlf.novell.com>

On Fri, Jun 07, 2013 at 04:43:52PM +0100, Jan Beulich wrote:
> >>> On 07.06.13 at 15:58, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Thu, Jun 06, 2013 at 02:14:45PM +0100, Jan Beulich wrote:
> >> Imo this is not a viable option - we shouldn't start peeking into the
> >> second module (which Linux uses as initrd, but which other OSes
> >> may use for other purposes) - so far this is just a binary blob to the
> >> hypervisor.
> >> 
> > 
> > I was under the impression that the code you introduced for microcode 
> > loading
> > was doing that exactly. Granted it would only peek if told to. Perhaps that
> > code can be expanded to scan the blob for cpio image of microcode in 
> > whatever it was told to look at?
> 
> No, this is a separate (usually third) grub module, containing just
> the raw microcode data (in the same format that otherwise would
> get passed down from Dom0 via hypercall).

Correct. What I was thinking would be beneficial is extend the code
such that if the user wishes - it could scan one of the grub modules
for a signature and if so, extract the relevant microcode from the
cpio image. Then apply it.

> 
> Jan
> 

      reply	other threads:[~2013-06-07 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 20:19 Linux 3.11 and the future Konrad Rzeszutek Wilk
2013-06-06  7:38 ` Jan Beulich
2013-06-06 13:07   ` Konrad Rzeszutek Wilk
2013-06-06 13:14     ` Jan Beulich
2013-06-07 13:58       ` Konrad Rzeszutek Wilk
2013-06-07 15:43         ` Jan Beulich
2013-06-07 17:03           ` Konrad Rzeszutek Wilk [this message]

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=20130607170352.GA3730@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Benjamin.Guthro@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=stefan.bader@canonical.com \
    --cc=xen-devel@lists.xen.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.