From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Borislav Petkov <bp@suse.de>
Cc: Juergen Gross <jgross@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Can't boot as Xen dom0 due to commit fe055896
Date: Thu, 15 Dec 2016 14:08:50 -0500 [thread overview]
Message-ID: <385ac3cd-7a3f-4c4d-69bb-8feee235fb7e@oracle.com> (raw)
In-Reply-To: <20161215173609.ornfok6lk5oro2pj@pd.tnic>
On 12/15/2016 12:36 PM, Borislav Petkov wrote:
> On Thu, Dec 15, 2016 at 12:27:49PM -0500, Boris Ostrovsky wrote:
>> It will probably fix it but I don't think we want this: it's a
>> build-time solution. Most kernels have XEN on even though they are
>> booted bare-metal.
> Lemme tell you want I want: a way to detect I'm running on xen. Does
> CPUID(4) work really early, at load_ucode_bsp() time?
>
> IOW, can I use some of the functionality hypervisor_cpuid_base() uses to
> detect xen and stop loading any further?
I think we need at least
diff --git a/arch/x86/kernel/cpu/microcode/amd.c
b/arch/x86/kernel/cpu/microcode/amd.c
index 6f353bd..383b635 100644
--- a/arch/x86/kernel/cpu/microcode/amd.c
+++ b/arch/x86/kernel/cpu/microcode/amd.c
@@ -427,7 +427,7 @@ int __init save_microcode_in_initrd_amd(unsigned int
fam)
{
enum ucode_state ret;
int retval = 0;
- u16 eq_id;
+ u16 eq_id = 0;
if (!cont.data) {
if (IS_ENABLED(CONFIG_X86_32) && (cont.size != -1)) {
This fixes my PV boot problem. I am still failing to boot HVM, will need
to look at this some more.
-boris
next prev parent reply other threads:[~2016-12-15 19:07 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
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 [this message]
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=385ac3cd-7a3f-4c4d-69bb-8feee235fb7e@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=jgross@suse.com \
--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