mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Juergen Gross <jgross@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.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: Fri, 16 Dec 2016 10:43:26 +0100	[thread overview]
Message-ID: <20161216094326.bnkr5a2k3njmdeyi@pd.tnic> (raw)
In-Reply-To: <29d252b8-67ff-bd61-f274-0ed75708cd55@suse.com>

On Fri, Dec 16, 2016 at 10:20:42AM +0100, Juergen Gross wrote:
> Without testing, but I doubt it is working. As pv guests aren't coming
> through check_loader_disabled_bsp() at all I can't see why your patch
> would work for dom0.

Do they go through check_loader_disabled_ap() ?

> Additionally I don't think you want to call native_cpuid() if
> have_cpuid_p() returns false.

Good point, fixed.

> So I think you want a generic "platform_allows_ucode_load()"
> function checking for support of cpuid and virtualization. This
> function should be called both in check_loader_disabled_bsp() and
> check_loader_disabled_ap() to bail out early.

See question above. If they go through check_loader_disabled_ap(),
then I'm inclined to set dis_ucode_ldr to true at build time and let
check_loader_disabled_bsp() set it to false on baremetal or if any of
the other checks pass.

If the pv guests run into check_loader_disabled_ap, then they'll see
dis_ucode_ldr true and return.

Ok?

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

  reply	other threads:[~2016-12-16  9:43 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
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 [this message]
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=20161216094326.bnkr5a2k3njmdeyi@pd.tnic \
    --to=bp@suse.de \
    --cc=boris.ostrovsky@oracle.com \
    --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

all inboxes | Powered by JetHome®