From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Juergen Gross" <jgross@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
Daniel Kiper <daniel.kiper@oracle.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Xen PVH support in grub2
Date: Mon, 6 Nov 2017 09:51:24 -0500 [thread overview]
Message-ID: <073e6470-f844-d22f-22ab-4d47500fdfb5@oracle.com> (raw)
In-Reply-To: <04a4c318-552c-da75-a372-15fc64fd395d@suse.com>
On 11/06/2017 02:16 AM, Juergen Gross wrote:
> On 03/11/17 20:00, Boris Ostrovsky wrote:
>> On 11/03/2017 02:40 PM, Juergen Gross wrote:
>>> On 03/11/17 19:35, Boris Ostrovsky wrote:
>>>> On 11/03/2017 02:23 PM, Juergen Gross wrote:
>>>>> On 03/11/17 19:19, Boris Ostrovsky wrote:
>>>>>> On 11/03/2017 02:05 PM, Juergen Gross wrote:
>>>>>>> So again the question: how to tell whether we are PVH or HVM in
>>>>>>> init_hypervisor_platform()? ACPi tables are scanned way later...
>>>>>> Can we make grub/OVMF append a boot option?
>>>>>>
>>>>>> Or set setup_header.hardware_subarch to something? We already have
>>>>>> X86_SUBARCH_XEN but it is only used by PV. Or we might be able to use
>>>>>> hardware_subarch_data (will need to get a buy-in from x86 maintainers, I
>>>>>> think).
>>>>> But wouldn't this break the idea to reuse the native boot paths in
>>>>> grub/OVMF without further modifications?
>>>> WDYM? We will have to have some sort of a plugin in either one to build
>>>> the zeropage anyway. So we'd set hardware_subarch there, in addition to
>>>> other things like setting memory and such.
>>> But isn't the zeropage already being built? I admit that setting subarch
>>> isn't a big deal, but using another entry with a passed-through pvh
>>> start struct isn't either...
>> I don't follow, sorry. My understanding is that zeropage will be built
>> by PVH-enlightened grub so part of this process would be setting the
>> subarch bit.
> My reasoning was based on Roger's remark:
>
> "OTOH if Linux is capable of booting from the native entry point inside
> of a PVH container, we would only have to port OVMF and grub in order
> to work inside of a PVH container, leaving the rest of the logic
> untouched."
Right, and in my mind porting OVMF/grub includes creating proper zeropage.
BTW, another option might be to "type_of_loader = (9 << 4) | 0", which
is what init_pvh_bootparams() does. In fact, whatever is done in the
firmware should probably match what that routine does.
-boris
next prev parent reply other threads:[~2017-11-06 14:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 14:46 Xen PVH support in grub2 Juergen Gross
2017-09-29 15:07 ` [Xen-devel] " George Dunlap
2017-09-29 15:24 ` Roger Pau Monné
2017-09-29 15:33 ` Juergen Gross
2017-09-29 15:51 ` Roger Pau Monné
2017-09-29 17:02 ` Boris Ostrovsky
2017-09-29 17:07 ` Roger Pau Monné
2017-09-29 17:22 ` Boris Ostrovsky
2017-10-03 8:56 ` Roger Pau Monné
2017-10-03 12:47 ` Boris Ostrovsky
2017-11-03 12:00 ` Juergen Gross
2017-11-03 12:17 ` Roger Pau Monné
2017-11-03 12:50 ` Juergen Gross
2017-11-03 14:07 ` Roger Pau Monné
2017-11-03 14:24 ` Juergen Gross
2017-11-03 14:36 ` Boris Ostrovsky
2017-11-03 14:59 ` Juergen Gross
2017-11-03 15:10 ` Boris Ostrovsky
2017-11-03 15:27 ` Juergen Gross
2017-11-03 18:05 ` Juergen Gross
2017-11-03 18:19 ` Boris Ostrovsky
2017-11-03 18:23 ` Juergen Gross
2017-11-03 18:35 ` Boris Ostrovsky
2017-11-03 18:40 ` Juergen Gross
2017-11-03 19:00 ` Boris Ostrovsky
2017-11-06 7:16 ` Juergen Gross
2017-11-06 14:51 ` Boris Ostrovsky [this message]
2017-11-06 15:05 ` Juergen Gross
2017-11-06 16:42 ` Boris Ostrovsky
2017-11-07 7:42 ` Juergen Gross
2017-11-07 16:10 ` Boris Ostrovsky
2017-11-09 5:01 ` Konrad Rzeszutek Wilk
2017-11-03 18:37 ` Roger Pau Monné
2017-11-03 18:47 ` Juergen Gross
2017-11-06 11:36 ` Juergen Gross
2017-11-07 14:49 ` Juergen Gross
2017-09-29 15:34 ` George Dunlap
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=073e6470-f844-d22f-22ab-4d47500fdfb5@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).