From: Maran Wilson <maran.wilson@oracle.com>
To: x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, jgross@suse.com
Cc: boris.ostrovsky@oracle.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, roger.pau@citrix.com, rkrcmar@redhat.com,
maran.wilson@oracle.com
Subject: [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code
Date: Mon, 16 Apr 2018 16:12:38 -0700 [thread overview]
Message-ID: <1523920360-27743-1-git-send-email-maran.wilson@oracle.com> (raw)
In-Reply-To: <1523920175-27287-1-git-send-email-maran.wilson@oracle.com>
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>
---
arch/x86/platform/pvh/enlighten.c | 5 ++---
arch/x86/xen/Makefile | 1 +
arch/x86/xen/enlighten_pvh.c | 9 +++++++++
3 files changed, 12 insertions(+), 3 deletions(-)
create mode 100644 arch/x86/xen/enlighten_pvh.c
diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c
index aa1c6a6831a9..74ff1c3d2789 100644
--- a/arch/x86/platform/pvh/enlighten.c
+++ b/arch/x86/platform/pvh/enlighten.c
@@ -17,10 +17,9 @@
/*
* PVH variables.
*
- * xen_pvh pvh_bootparams and pvh_start_info need to live in data segment
- * since they are used after startup_{32|64}, which clear .bss, are invoked.
+ * pvh_bootparams and pvh_start_info need to live in the data segment since
+ * 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 hvm_start_info pvh_start_info __attribute__((section(".data")));
diff --git a/arch/x86/xen/Makefile b/arch/x86/xen/Makefile
index f1b850607212..ae5c6f1f0fe0 100644
--- a/arch/x86/xen/Makefile
+++ b/arch/x86/xen/Makefile
@@ -20,6 +20,7 @@ obj-y := enlighten.o multicalls.o mmu.o irq.o \
obj-$(CONFIG_XEN_PVHVM) += enlighten_hvm.o mmu_hvm.o suspend_hvm.o
obj-$(CONFIG_XEN_PV) += setup.o apic.o pmu.o suspend_pv.o \
p2m.o enlighten_pv.o mmu_pv.o
+obj-$(CONFIG_XEN_PVH) += enlighten_pvh.o
obj-$(CONFIG_EVENT_TRACING) += trace.o
diff --git a/arch/x86/xen/enlighten_pvh.c b/arch/x86/xen/enlighten_pvh.c
new file mode 100644
index 000000000000..313fe499065e
--- /dev/null
+++ b/arch/x86/xen/enlighten_pvh.c
@@ -0,0 +1,9 @@
+#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;
--
2.16.1
next prev parent reply other threads:[~2018-04-16 23:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 23:09 [PATCH v7 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-04-16 23:11 ` [PATCH v7 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-04-17 6:18 ` Juergen Gross
2018-04-16 23:11 ` [PATCH v7 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-04-17 6:24 ` Juergen Gross
2018-04-16 23:12 ` Maran Wilson [this message]
2018-04-17 6:29 ` [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code Juergen Gross
2018-04-16 23:12 ` [PATCH v7 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-04-16 23:12 ` [PATCH v7 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-04-16 23:13 ` [PATCH v7 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-04-17 6:30 ` Juergen Gross
2018-04-16 23:13 ` [PATCH v7 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-04-17 6:41 ` Juergen Gross
2018-04-18 8:11 ` [PATCH v7 0/7] " Linus Walleij
2018-05-02 21:37 ` Maran Wilson
2018-05-16 20:27 ` Maran Wilson
2018-05-18 11:31 ` Paolo Bonzini
2018-05-23 16:56 ` Maran Wilson
2018-11-16 10:46 ` Paolo Bonzini
2018-11-16 17:17 ` Maran Wilson
2018-11-19 18:25 ` 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=1523920360-27743-1-git-send-email-maran.wilson@oracle.com \
--to=maran.wilson@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=roger.pau@citrix.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®