[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cef985c3-a687-c1af-83ac-2c71af45a366@redhat.com>
Date: Fri, 7 Dec 2018 00:30:44 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Maran Wilson <maran.wilson@...cle.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
kvm@...r.kernel.org, jgross@...e.com
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
jpoimboe@...hat.com, kirill.shutemov@...ux.intel.com, bp@...e.de,
thomas.lendacky@....com, luto@...nel.org,
dave.hansen@...ux.intel.com, roger.pau@...rix.com,
rkrcmar@...hat.com, rdunlap@...radead.org
Subject: Re: [PATCH v8 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and
CONFIG_XEN_PVH
On 07/12/18 00:11, Boris Ostrovsky wrote:
> On 12/6/18 5:49 PM, Paolo Bonzini wrote:
>> On 06/12/18 23:34, Boris Ostrovsky wrote:
>>> On 12/6/18 5:11 PM, Paolo Bonzini wrote:
>>>
>>>> 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?
>> Can you? It's a completely different binary format, the EFI handover
>> protocol is invoked via a special entry point and needs the Linux header
>> format, not ELF.
>
> Right, but I think it is desirable to be able to build both from the
> same config file.
Ah, "make bzImage" and use the vmlinux for PVH, because PVH fetches the
entry point from the special note. That's clever. :)
I don't see why it should not work, and if so the "depends on !EFI" is
indeed unnecessary.
Paolo
Powered by blists - more mailing lists