[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0fd8799-35ea-fba5-9d0d-94feead85943@redhat.com>
Date: Fri, 7 Dec 2018 14:52:55 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Juergen Gross <jgross@...e.com>,
Maran Wilson <maran.wilson@...cle.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
kvm@...r.kernel.org
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
boris.ostrovsky@...cle.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 14:50, Juergen Gross wrote:
> The PVH boot entry is in the same bzImage binary as the normal one.
> Its just another entry, similar to the Xen PV boot entry. So the binary
> arch/x86/boot/bzimage can be booted either on bare metal via grub2 or
> other boot-loaders, as Xen PV-guest, as Xen PVH-guest, or as KVM
> PVH-guest. So one build and one binary. The non-standard boot entries
> (PV- or PVH-node) are found via ELF-notes by the boot loader (qemu in
> case of KVM).
>
But the bzImage is not an ELF binary, and it is compressed, isn't it?
/me is confused. :)
Paolo
Powered by blists - more mailing lists