From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Borislav Petkov <bp@suse.de>
Cc: Juergen Gross <JGross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Can't boot as Xen dom0 due to commit fe055896
Date: Thu, 15 Dec 2016 16:59:49 +0000 [thread overview]
Message-ID: <1759e235-b514-7a5d-4eae-e898437bdbd2@citrix.com> (raw)
In-Reply-To: <5852D8A20200007800129CC6@prv-mh.provo.novell.com>
On 15/12/16 16:53, Jan Beulich wrote:
>>>> On 15.12.16 at 17:46, <bp@suse.de> wrote:
>> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>>> with today's kernel the system isn't coming up when booted as Xen dom0:
>> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
>> hypervisor supposed to apply microcode?
> Yes, it's the hypervisor. Dom0 can at best hand the blob to it via
> hypercall, but iirc upstream Linux doesn't make use of that.
Xen has the same logic as Linux does to look for an uncompressed
microcode blob in the initrd and apply it early in boot.
If dom0 goes looking, it should see the same microcode version as it has
in its initrd.
~Andrew
next prev parent reply other threads:[~2016-12-15 16:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:12 Juergen Gross
2016-12-15 16:46 ` Borislav Petkov
2016-12-15 16:53 ` [Xen-devel] " Jan Beulich
2016-12-15 16:59 ` Andrew Cooper [this message]
2016-12-15 17:14 ` Borislav Petkov
2016-12-15 17:00 ` Boris Ostrovsky
2016-12-15 17:17 ` Borislav Petkov
2016-12-15 17:27 ` Boris Ostrovsky
2016-12-15 17:36 ` Borislav Petkov
2016-12-15 19:08 ` Boris Ostrovsky
2016-12-15 19:23 ` Borislav Petkov
2016-12-15 19:36 ` Boris Ostrovsky
2016-12-15 20:03 ` Borislav Petkov
2016-12-15 22:56 ` Boris Ostrovsky
2016-12-15 23:04 ` Borislav Petkov
2016-12-16 3:56 ` Boris Ostrovsky
2016-12-16 9:01 ` Borislav Petkov
2016-12-16 9:14 ` [Xen-devel] " Andrew Cooper
2016-12-16 4:14 ` Henrique de Moraes Holschuh
2016-12-16 7:28 ` Juergen Gross
2016-12-16 9:02 ` Borislav Petkov
2016-12-16 9:20 ` Juergen Gross
2016-12-16 9:43 ` Borislav Petkov
2016-12-16 10:00 ` Juergen Gross
2016-12-16 10:45 ` Borislav Petkov
2016-12-16 12:15 ` Juergen Gross
2016-12-16 12:19 ` Borislav Petkov
2016-12-16 13:07 ` Borislav Petkov
2016-12-16 14:40 ` Boris Ostrovsky
2016-12-16 15:17 ` Borislav Petkov
2016-12-15 17:06 ` Juergen Gross
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=1759e235-b514-7a5d-4eae-e898437bdbd2@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome