For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
uncompressed Linux kernel binary without the need to run firmware.
There already exists
On 11/29/2017 12:59 AM, Paolo Bonzini wrote:
On 28/11/2017 20:34, Maran Wilson wrote:
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
On 11/29/2017 12:21 AM, Juergen Gross wrote:
On 28/11/17 20:34, Maran Wilson wrote:
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
On 11/29/2017 6:44 AM, Paolo Bonzini wrote:
I actually like this patch, except that I'd get the e820 memory map from
fw_cfg (see the first part of
https://github.com/bonzini/qboot/blob/master/fw_cfg.c, and extract_e820
inhttps://github.com/bonzini/qboot/blob/master/main.c) instead of the
second m
lt without CONFIG_XEN to start KVM guests via the
PVH entry point. If the latter, any suggestions for which common files or
directories I can move this stuff to?
Maran Wilson (2):
xen/pvh: Add memory map pointer to hvm_start_info struct
KVM: x86: Allow Qemu/KVM to use PVH entry point
ar
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
uncompressed Linux kernel binary without the need to run firmware.
There already exists
The start info structure that is defined as part of the x86/HVM direct
boot ABI and used for starting Xen PVH guests would be more versatile if
it also included a way to efficiently pass information about the memory
map to the guest.
That way Xen PVH guests would not be forced to use a hypercall t
24
Thanks,
-Maran
On 12/1/2017 12:08 AM, Paolo Bonzini wrote:
On 30/11/2017 19:23, Maran Wilson wrote:
Are you saying the Linux PVH entry code (such as init_pvh_bootparams())
should use the fw_cfg interface to read the e820 memory map data and put
it into the zeropage? Basically, keeping th
Thanks for taking a look Jan. More below...
On 12/8/2017 12:49 AM, Jan Beulich wrote:
On 07.12.17 at 23:45, wrote:
The start info structure that is defined as part of the x86/HVM direct
boot ABI and used for starting Xen PVH guests would be more versatile if
it also included a way to efficient
v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cases.
Maran Wilson (2):
xen/pvh: Add memory map pointer to hvm_start_info struct
KVM: x86: Allow Qemu/KVM to use
The start info structure that is defined as part of the x86/HVM direct
boot ABI and used for starting Xen PVH guests would be more versatile if
it also included a way to pass information about the memory map to the
guest. This would allow KVM guests to share the same entry point.
---
include/xen/i
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
uncompressed Linux kernel binary without the need to run firmware.
There already exists
On 1/9/2019 11:53 AM, Boris Ostrovsky wrote:
On 1/9/19 6:53 AM, Stefano Garzarella wrote:
Hi Liam,
On Tue, Jan 8, 2019 at 3:47 PM Liam Merwick wrote:
QEMU sets the hvm_modlist_entry in load_linux() after the call to
load_elfboot() and then qboot loads it in boot_pvh_from_fw_cfg()
But the cur
CONFIG_XEN.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/Kconfig | 6 ++
arch/x86/kernel/head_64.S | 2 +-
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 8689e794a43c
he second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cases.
Maran Wilson (7):
xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH
xen/pvh: Move PVH entry code out of Xen specific tree
xen/pvh: Create a new file
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
arch/x86
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/platform/pvh/enlighten.c | 29
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
MAINTAINERS
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
Suggested-by: Konrad Rzeszutek Wilk
Suggested
: Maran Wilson
Reviewed-by: Juergen Gross
---
include/xen/interface/hvm/start_info.h | 63 +-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/include/xen/interface/hvm/start_info.h
b/include/xen/interface/hvm/start_info.h
index 648415976ead
On 12/5/2018 2:37 PM, Liam Merwick wrote:
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, QEMU should be able to boot directly into the
uncompressed Linux kernel binary with minimal
On 12/7/2018 7:14 AM, Paolo Bonzini wrote:
On 07/12/18 14:58, Juergen Gross wrote:
On 07/12/2018 14:52, Paolo Bonzini wrote:
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
CONFIG_XEN.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/Kconfig | 6 ++
arch/x86/kernel/head_64.S | 2 +-
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 8689e794a43c
v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cases.
Maran Wilson (7):
xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH
xen/pvh: Move PVH entry
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
arch/x86
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/platform/pvh/enlighten.c | 29
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
MAINTAINERS
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86
: Maran Wilson
Reviewed-by: Juergen Gross
---
include/xen/interface/hvm/start_info.h | 63 +-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/include/xen/interface/hvm/start_info.h
b/include/xen/interface/hvm/start_info.h
index 648415976ead
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
Suggested-by: Konrad Rzeszutek Wilk
Suggested
On 12/11/2018 9:11 AM, Stefano Garzarella wrote:
Hi Liam,
in order to support PVH also with SeaBIOS, I'm going to work on a new
option rom (like linuxboot/multiboot) that can be used in this case.
That is awesome. Yes, please keep us posted when you have something working.
Just FYI, before swi
On 12/11/2018 5:18 AM, Borislav Petkov wrote:
On Mon, Dec 10, 2018 at 11:05:34AM -0800, Maran Wilson wrote:
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to
On 12/12/2018 7:28 AM, Stefano Garzarella wrote:
On Tue, Dec 11, 2018 at 7:35 PM Maran Wilson wrote:
On 12/11/2018 9:11 AM, Stefano Garzarella wrote:
Hi Liam,
in order to support PVH also with SeaBIOS, I'm going to work on a new
option rom (like linuxboot/multiboot) that can be used in
On 12/6/2018 1:21 PM, Paolo Bonzini wrote:
On 06/12/18 07:02, Maran Wilson wrote:
For certain applications it is desirable to rapidly boot a KVM virtual
machine. In cases where legacy hardware and software support within the
guest is not needed, Qemu should be able to boot directly into the
On 12/12/2018 12:39 PM, Borislav Petkov wrote:
On Tue, Dec 11, 2018 at 11:29:21AM -0800, Maran Wilson wrote:
Is your question about what options you need to provide to Qemu? Or is your
question about the SW implementation choices?
Assuming the former...
Yeah, that's what I wanted to
: Maran Wilson
Reviewed-by: Roger Pau Monné
Acked-by: Jan Beulich
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Boris Ostrovsky
Cc: Roger Pau Monné
---
xen/include/public/arch-x86/hvm/start_info.h | 63 +++-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/xen
From: Boris Ostrovsky
Signed-off-by: Boris Ostrovsky
Signed-off-by: Maran Wilson
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Roger Pau Monné
Cc: Boris Ostrovsky
Cc: Maran Wilson
---
Changes in v5:
* Fix calculation of start_info_size (and move it from under
"if(!dom->device_model)&q
strovsky
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Roger Pau Monné
Cc: Boris Ostrovsky
Cc: Maran Wilson
---
Changes in v5:
* Adjusted call interfaces to take into account the fact that
libxl_domain_build_info is pointed to from libxl_domain_config.
---
tools/libxl/libxl_arch.h | 10 ++--
From: Boris Ostrovsky
We will later copy it to hvm_start_info.
(Also remove stale comment claming that xc_dom_image.start_info_seg is
only used for HVMlite guests)
Signed-off-by: Boris Ostrovsky
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Roger Pau Monné
Cc: Boris Ostrovsky
Cc: Maran Wilson
VH guests via hvm_start_info
Maran Wilson (1):
x86/PVHv2: Add memory map pointer to hvm_start_info struct
tools/libxc/include/xc_dom.h | 7 +++-
tools/libxc/xc_dom_x86.c | 29 +
tools/libxl/libxl_arch.h | 10 +
tools/libx
omments as
suggested by Jan.
Changes from v1:
* Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cases.
Maran Wil
CONFIG_XEN.
Signed-off-by: Maran Wilson
---
arch/x86/Kconfig | 6 ++
arch/x86/kernel/head_64.S | 2 +-
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 27fede438959..e3b836d7ad09 100644
--- a
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
---
MAINTAINERS| 1 +
arch/x86
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
---
arch/x86/platform/pvh/enlighten.c | 5
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
arch/x86
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/platform/pvh/enlighten.c | 28
: Maran Wilson
---
include/xen/interface/hvm/start_info.h | 63 +-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/include/xen/interface/hvm/start_info.h
b/include/xen/interface/hvm/start_info.h
index 648415976ead..50af9ea2ff1e 100644
--- a/include/xen
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
Suggested-by: Konrad Rzeszutek Wilk
Suggested
hanges to comments as
suggested by Jan.
Changes from v1:
* Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cases.
CONFIG_XEN.
Signed-off-by: Maran Wilson
---
arch/x86/Kconfig | 6 ++
arch/x86/kernel/head_64.S | 2 +-
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index d234cca296db..8511d419e39f 100644
--- a
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
---
MAINTAINERS| 1 +
arch/x86
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
arch/x86
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/platform/pvh/enlighten.c | 29
: Maran Wilson
---
include/xen/interface/hvm/start_info.h | 63 +-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/include/xen/interface/hvm/start_info.h
b/include/xen/interface/hvm/start_info.h
index 648415976ead..50af9ea2ff1e 100644
--- a/include/xen
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
---
arch/x86/platform/pvh/enlighten.c | 5
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
Suggested-by: Konrad Rzeszutek Wilk
Suggested
On 4/18/2018 1:11 AM, Linus Walleij wrote:
I wonder why I am starting to get CCed on Xen patches all of a sudden.
I happened to run into Jürgen at a conference only last weekend, but
I still don't know anything whatsoever about Xen or how it works.
If get_maintainer.pl has started to return my
/2/28/1121
Maran Wilson (1):
x86/PVHv2: Add memory map pointer to hvm_start_info struct
xen/include/public/arch-x86/hvm/start_info.h | 51 +-
1 file changed, 50 insertions(+), 1 deletion(-)
___
Xen-devel mailing list
Xen-devel
: Maran Wilson
---
xen/include/public/arch-x86/hvm/start_info.h | 51 +++-
1 file changed, 50 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/arch-x86/hvm/start_info.h
b/xen/include/public/arch-x86/hvm/start_info.h
index 6484159..ae8dac8 100644
--- a/xen/include
On 3/2/2018 1:20 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Mar 02, 2018 at 12:54:29PM -0800, Maran Wilson wrote:
The start info structure that is defined as part of the x86/HVM direct boot
ABI and used for starting Xen PVH guests would be more versatile if it also
included a way to pass
On 3/13/2018 3:50 AM, Roger Pau Monné wrote:
On Fri, Mar 02, 2018 at 12:54:29PM -0800, Maran Wilson wrote:
The start info structure that is defined as part of the x86/HVM direct boot
ABI and used for starting Xen PVH guests would be more versatile if it also
included a way to pass information
On 3/13/2018 9:34 AM, Jan Beulich wrote:
On 13.03.18 at 17:20, wrote:
On 3/13/2018 3:50 AM, Roger Pau Monné wrote:
On Fri, Mar 02, 2018 at 12:54:29PM -0800, Maran Wilson wrote:
@@ -62,10 +72,34 @@
*| reserved |
* 32 ++
*
+ * The layout of each entry in
On 3/13/2018 10:16 AM, Roger Pau Monné wrote:
On Tue, Mar 13, 2018 at 09:55:20AM -0700, Maran Wilson wrote:
On 3/13/2018 9:34 AM, Jan Beulich wrote:
On 13.03.18 at 17:20, wrote:
On 3/13/2018 3:50 AM, Roger Pau Monné wrote:
On Fri, Mar 02, 2018 at 12:54:29PM -0800, Maran Wilson wrote
From: Boris Ostrovsky
We will later copy it to hvm_start_info.
(Also remove stale comment claming that xc_dom_image.start_info_seg is
only used for HVMlite guests)
Signed-off-by: Boris Ostrovsky
---
tools/libxc/include/xc_dom.h | 8 +++-
tools/libxl/libxl_x86.c | 6 ++
2 files ch
From: Boris Ostrovsky
Signed-off-by: Boris Ostrovsky
---
tools/libxc/xc_dom_x86.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
index 0b65dab..4f4b26e 100644
--- a/tools/libxc/xc_dom_x86.c
+++ b/tool
: Maran Wilson
---
xen/include/public/arch-x86/hvm/start_info.h | 63 +++-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/arch-x86/hvm/start_info.h
b/xen/include/public/arch-x86/hvm/start_info.h
index 6484159..f8d6a1a 100644
--- a/xen/include
image
libxc: Pass e820 map to PVH guest via hvm_start_info
Maran Wilson (1):
x86/PVHv2: Add memory map pointer to hvm_start_info struct
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinf
From: Boris Ostrovsky
Since hvm_start_info has now been expanded to include PVH guest's
memory map (i.e. e820) we need to know size of this map by the time we
create dom->start_info_seg in alloc_magic_pages_hvm().
To do so we have to call libxl__arch_domain_construct_memmap() earlier,
before xc_
On 3/14/2018 10:28 AM, Boris Ostrovsky wrote:
On 03/14/2018 03:55 AM, Jan Beulich wrote:
On 14.03.18 at 00:31, wrote:
+ * For x86 implementations at least, the values used in the type field will
+ * match the Address Range Types as defined in section 15 (System Address
+ * Map Interfaces) of t
libxc: Pass e820 map to PVH guest via hvm_start_info
Maran Wilson (1):
x86/PVHv2: Add memory map pointer to hvm_start_info struct
tools/libxc/include/xc_dom.h | 8 +++-
tools/libxc/xc_dom_x86.c | 30 -
tools/libxl/libxl_create.c
: Maran Wilson
---
xen/include/public/arch-x86/hvm/start_info.h | 66 +++-
1 file changed, 65 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/arch-x86/hvm/start_info.h
b/xen/include/public/arch-x86/hvm/start_info.h
index 6484159..f2e8ba6 100644
--- a/xen/include
From: Boris Ostrovsky
Signed-off-by: Boris Ostrovsky
Signed-off-by: Maran Wilson
---
tools/libxc/xc_dom_x86.c | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
index 0b65dab..b46bd1d 100644
From: Boris Ostrovsky
We will later copy it to hvm_start_info.
(Also remove stale comment claming that xc_dom_image.start_info_seg is
only used for HVMlite guests)
Signed-off-by: Boris Ostrovsky
---
tools/libxc/include/xc_dom.h | 8 +++-
tools/libxl/libxl_x86.c | 6 ++
2 files ch
From: Boris Ostrovsky
Since hvm_start_info has now been expanded to include PVH guest's
memory map (i.e. e820) we need to know size of this map by the time we
create dom->start_info_seg in alloc_magic_pages_hvm().
To do so we have to call libxl__arch_domain_construct_memmap() earlier,
before xc_
On 3/16/2018 4:11 AM, Roger Pau Monné wrote:
On Thu, Mar 15, 2018 at 02:33:09PM -0700, Maran Wilson wrote:
The start info structure that is defined as part of the x86/HVM direct boot
ABI and used for starting Xen PVH guests would be more versatile if it also
included a way to pass information
From: Boris Ostrovsky
Since hvm_start_info has now been expanded to include memory map (i.e.
e820) we need to know size of this map by the time we create
dom->start_info_seg in alloc_magic_pages_hvm().
To do so we have to call libxl__arch_domain_construct_memmap() earlier,
before xc_dom_build_im
From: Boris Ostrovsky
Signed-off-by: Boris Ostrovsky
Signed-off-by: Maran Wilson
---
tools/libxc/xc_dom_x86.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
index 0b65dab..b2d8403 100644
to HVM/PVH guests via hvm_start_info
Maran Wilson (1):
x86/PVHv2: Add memory map pointer to hvm_start_info struct
tools/libxc/include/xc_dom.h | 7 ++-
tools/libxc/xc_dom_x86.c | 29 -
tools/libxl/libxl_arch.h | 9 +---
t
: Maran Wilson
---
xen/include/public/arch-x86/hvm/start_info.h | 65 +++-
1 file changed, 64 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/arch-x86/hvm/start_info.h
b/xen/include/public/arch-x86/hvm/start_info.h
index 6484159..d491f2d 100644
--- a/xen/include
From: Boris Ostrovsky
We will later copy it to hvm_start_info.
(Also remove stale comment claming that xc_dom_image.start_info_seg is
only used for HVMlite guests)
Signed-off-by: Boris Ostrovsky
---
tools/libxc/include/xc_dom.h | 7 ++-
tools/libxl/libxl_x86.c | 4
2 files chang
nges to comments as
suggested by Jan.
Changes from v1:
* Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
cas
CONFIG_XEN.
Signed-off-by: Maran Wilson
---
arch/x86/Kconfig | 7 +++
arch/x86/kernel/head_64.S | 4 ++--
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index eb7f43f23521..58831320b5d2 100644
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
---
arch/x86/platform/pvh/enlighten.c | 5
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Juergen Gross
---
arch/x86
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
Reviewed-by: Konrad Rzeszutek Wilk
---
MAINTAINERS| 1 +
arch/x86
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
---
arch/x86/platform/pvh/enlighten.c | 28
: Maran Wilson
---
include/xen/interface/hvm/start_info.h | 65 +-
1 file changed, 64 insertions(+), 1 deletion(-)
diff --git a/include/xen/interface/hvm/start_info.h
b/include/xen/interface/hvm/start_info.h
index 648415976ead..d491f2d89393 100644
--- a/include/xen
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
Suggested-by: Konrad Rzeszutek Wilk
Suggested
On 3/20/2018 12:23 PM, Randy Dunlap wrote:
Hi,
On 03/20/2018 12:18 PM, Maran Wilson wrote:
In order to pave the way for hypervisors other then Xen to use the PVH
than
entry point for VMs, we need to factor the PVH entry code into Xen
On 3/21/2018 2:40 AM, Juergen Gross wrote:
On 21/03/18 10:28, Roger Pau Monné wrote:
On Tue, Mar 20, 2018 at 09:48:56AM -0700, Maran Wilson wrote:
+/*
* C representation of the x86/HVM start info layout.
*
* The canonical definition of this layout is above, this is just a way to
.
* Removed the "packed" attributes and made changes to comments as
suggested by Jan.
Changes from v1:
* Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things
On 5/18/2018 4:31 AM, Paolo Bonzini wrote:
On 16/05/2018 22:27, Maran Wilson wrote:
Friendly ping. I am hopeful one of the x86 and/or KVM maintainers has a
few cycles to spare to look this over.
And thanks to everyone who has helped thus far by providing valuable
feedback and reviewing
CONFIG_XEN.
Signed-off-by: Maran Wilson
---
arch/x86/Kconfig | 8
arch/x86/kernel/head_64.S | 4 ++--
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index eb7f43f23521..fa7cd0305125 100644
into the Xen specific file. This will allow us
to compile kernels in the future without CONFIG_XEN that are still capable
of being booted as a Qemu/KVM guest via the PVH entry point.
Signed-off-by: Maran Wilson
---
arch/x86/pvh.c | 28 ++--
arch/x86/xen
t; attributes and made changes to comments as
suggested by Jan.
Changes from v1:
* Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
e820 map instead of using the second module entry to pass the table.
* Cleaned things up a bit to reduce the number of xen vs non-xen special
We need to refactor PVH entry code so that support for other hypervisors
like Qemu/KVM can be added more easily.
The first step in that direction is to create a new file that will
eventually hold the Xen specific routines.
Signed-off-by: Maran Wilson
---
arch/x86/pvh.c | 1
sitting at a higher level in the tree.
This patch is not introducing any code or functional changes, just moving
files from one location to another.
Signed-off-by: Maran Wilson
---
MAINTAINERS | 1 +
arch/x86/Kbuild | 3 +++
arch/x86/{xen/xen
. Moving it out of the common file
is going to allow us to compile kernels in the future without CONFIG_XEN
that are still capable of being booted as a Qemu/KVM guest via the PVH
entry point.
Signed-off-by: Maran Wilson
---
arch/x86/pvh.c | 28
arch/x86/xen
an ABI to allow this for Xen PVH guests and the ABI
is supported by Linux and FreeBSD:
https://xenbits.xen.org/docs/unstable/misc/pvh.html
This patch enables Qemu to use that same entry point for booting KVM
guests.
Signed-off-by: Maran Wilson
---
arch/x86/Kbuild | 4 ++--
arch/x86/pvh.c
1 - 100 of 106 matches
Mail list logo
