From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Maran Wilson <maran.wilson@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org, kvm@vger.kernel.org,
jgross@suse.com
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
jpoimboe@redhat.com, kirill.shutemov@linux.intel.com, bp@suse.de,
thomas.lendacky@amd.com, luto@kernel.org,
dave.hansen@linux.intel.com, roger.pau@citrix.com,
rkrcmar@redhat.com, rdunlap@infradead.org
Subject: Re: [PATCH v8 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH
Date: Thu, 6 Dec 2018 17:34:46 -0500 [thread overview]
Message-ID: <3b4fdddd-67d8-30d3-2a5d-c4d07b6f31c9@oracle.com> (raw)
In-Reply-To: <d532f023-85f9-62b9-ca56-53a619fdcd1e@redhat.com>
On 12/6/18 5:11 PM, Paolo Bonzini wrote:
> On 06/12/18 07:04, Maran Wilson wrote:
>> +config PVH
>> + bool "Support for running PVH guests"
>> + ---help---
>> + This option enables the PVH entry point for guest virtual machines
>> + as specified in the x86/HVM direct boot ABI.
>> +
> IIUC this breaks "normal" bzImage boot, so we should have something like
>
> The resulting kernel will not boot with most x86 boot loaders
> such as GRUB
Grub support for PVH guests (for Xen) is well under way.
> or SYSLINUX. Unless you plan to start the kernel
> using QEMU or Xen, you probably want to say N here.
I think PVH should not be user-selectable at all. It should be selected
by either XEN_PVH or KVM_GUEST_PVH (which you suggested to drop).
>
> and also
>
> depends on !EFI
>
> because even though in principle it would be possible to write a PVH
> loader for UEFI, PVH's start info does not support the EFI handover
> protocol.
But we should be able to build the binary with both EFI and PVH?
-boris
next prev parent reply other threads:[~2018-12-06 22:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 6:02 [PATCH v8 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-06 6:04 ` [PATCH v8 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-12-06 22:11 ` Paolo Bonzini
2018-12-06 22:34 ` Boris Ostrovsky [this message]
2018-12-06 22:49 ` Paolo Bonzini
2018-12-06 23:11 ` Boris Ostrovsky
2018-12-06 23:30 ` Paolo Bonzini
2018-12-06 23:36 ` [Xen-devel] " Andrew Cooper
2018-12-07 6:02 ` Juergen Gross
2018-12-07 13:41 ` Paolo Bonzini
2018-12-07 13:50 ` Juergen Gross
2018-12-07 13:52 ` Paolo Bonzini
2018-12-07 13:58 ` Juergen Gross
2018-12-07 15:14 ` Paolo Bonzini
2018-12-07 18:21 ` Maran Wilson
2018-12-06 6:04 ` [PATCH v8 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-12-06 6:05 ` [PATCH v8 3/7] xen/pvh: Create a new file for Xen specific PVH code Maran Wilson
2018-12-06 6:05 ` [PATCH v8 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-12-06 6:05 ` [PATCH v8 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-12-06 6:06 ` [PATCH v8 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-12-06 6:06 ` [PATCH v8 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-06 22:05 ` Paolo Bonzini
2018-12-06 21:21 ` [PATCH v8 0/7] " Paolo Bonzini
2018-12-06 21:37 ` Borislav Petkov
2018-12-06 21:58 ` Boris Ostrovsky
2018-12-06 22:14 ` Paolo Bonzini
2018-12-07 10:25 ` Borislav Petkov
2018-12-07 16:07 ` [Xen-devel] " Boris Ostrovsky
2018-12-07 19:22 ` Borislav Petkov
2018-12-12 18:09 ` Maran Wilson
2018-12-12 18:17 ` Boris Ostrovsky
2018-12-13 13:13 ` Paolo Bonzini
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=3b4fdddd-67d8-30d3-2a5d-c4d07b6f31c9@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maran.wilson@oracle.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=roger.pau@citrix.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).