xen/pvh: Create a new file for Xen specific PVH code
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 <maran.wilson@oracle.com> Reviewed-by: Juergen Gross <jgross@suse.com> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>hifive-unleashed-5.1
parent
fcd4747698
commit
4df7363e52
|
@ -18,10 +18,9 @@
|
||||||
/*
|
/*
|
||||||
* PVH variables.
|
* PVH variables.
|
||||||
*
|
*
|
||||||
* xen_pvh pvh_bootparams and pvh_start_info need to live in data segment
|
* pvh_bootparams and pvh_start_info need to live in the data segment since
|
||||||
* since they are used after startup_{32|64}, which clear .bss, are invoked.
|
* they are used after startup_{32|64}, which clear .bss, are invoked.
|
||||||
*/
|
*/
|
||||||
bool xen_pvh __attribute__((section(".data"))) = 0;
|
|
||||||
struct boot_params pvh_bootparams __attribute__((section(".data")));
|
struct boot_params pvh_bootparams __attribute__((section(".data")));
|
||||||
struct hvm_start_info pvh_start_info __attribute__((section(".data")));
|
struct hvm_start_info pvh_start_info __attribute__((section(".data")));
|
||||||
|
|
||||||
|
|
|
@ -36,6 +36,8 @@ obj-$(CONFIG_XEN_PV) += multicalls.o
|
||||||
obj-$(CONFIG_XEN_PV) += xen-asm.o
|
obj-$(CONFIG_XEN_PV) += xen-asm.o
|
||||||
obj-$(CONFIG_XEN_PV) += xen-asm_$(BITS).o
|
obj-$(CONFIG_XEN_PV) += xen-asm_$(BITS).o
|
||||||
|
|
||||||
|
obj-$(CONFIG_XEN_PVH) += enlighten_pvh.o
|
||||||
|
|
||||||
obj-$(CONFIG_EVENT_TRACING) += trace.o
|
obj-$(CONFIG_EVENT_TRACING) += trace.o
|
||||||
|
|
||||||
obj-$(CONFIG_SMP) += smp.o
|
obj-$(CONFIG_SMP) += smp.o
|
||||||
|
|
|
@ -0,0 +1,10 @@
|
||||||
|
// SPDX-License-Identifier: GPL-2.0
|
||||||
|
#include <linux/types.h>
|
||||||
|
|
||||||
|
/*
|
||||||
|
* PVH variables.
|
||||||
|
*
|
||||||
|
* The variable xen_pvh needs to live in the data segment since it is used
|
||||||
|
* after startup_{32|64} is invoked, which will clear the .bss segment.
|
||||||
|
*/
|
||||||
|
bool xen_pvh __attribute__((section(".data"))) = 0;
|
Loading…
Reference in New Issue