From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Jones <drjones@redhat.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: [PATCH RFC 0/1] Introduce VCPUOP_reset_vcpu_info
Date: Wed, 6 Aug 2014 15:08:21 +0200 [thread overview]
Message-ID: <1407330502-18768-1-git-send-email-vkuznets@redhat.com> (raw)
New VCPUOP_reset_vcpu_info is required to support kexec performed by smp pvhvm
guest. I'm sending almost unmodified version of Konrad's prototype. It was
tested with the following guest code:
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index c3a67c9..d90addb 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -183,8 +183,6 @@ static void xen_vcpu_setup(int cpu)
* This path is called twice on PVHVM - first during bootup via
* smp_init -> xen_hvm_cpu_notify, and then if the VCPU is being
* hotplugged: cpu_up -> xen_hvm_cpu_notify.
- * As we can only do the VCPUOP_register_vcpu_info once lets
- * not over-write its result.
*
* For PV it is called during restore (xen_vcpu_restore) and bootup
* (xen_setup_vcpu_info_placement). The hotplug mechanism does not
@@ -207,14 +205,23 @@ static void xen_vcpu_setup(int cpu)
info.mfn = arbitrary_virt_to_mfn(vcpup);
info.offset = offset_in_page(vcpup);
+ /*
+ * Call VCPUOP_reset_vcpu_info before VCPUOP_register_vcpu_info, this
+ * is required if we boot after kexec.
+ */
+
+ if (cpu != 0) {
+ err = HYPERVISOR_vcpu_op(VCPUOP_reset_vcpu_info, cpu, NULL);
+ if (err)
+ pr_warn("VCPUOP_reset_vcpu_info for CPU%d failed: %d\n",
+ cpu, err);
+ }
+
/* Check to see if the hypervisor will put the vcpu_info
structure where we want it, which allows direct access via
a percpu-variable.
- N.B. This hypercall can _only_ be called once per CPU. Subsequent
- calls will error out with -EINVAL. This is due to the fact that
- hypervisor has no unregister variant and this hypercall does not
- allow to over-write info.mfn and info.offset.
*/
+
err = HYPERVISOR_vcpu_op(VCPUOP_register_vcpu_info, cpu, &info);
if (err) {
@@ -228,6 +235,22 @@ static void xen_vcpu_setup(int cpu)
}
}
+void xen_teardown_vcpu_setup(int cpu)
+{
+ int err;
+
+ if (!have_vcpu_info_placement)
+ return;
+
+ err = HYPERVISOR_vcpu_op(VCPUOP_reset_vcpu_info, cpu, NULL);
+ if (err) {
+ xen_raw_printk("%s: VCPUOP_reset_vcpu_info rc: %d\n", __func__, err);
+ return;
+ }
+ if (cpu < MAX_VIRT_CPUS)
+ per_cpu(xen_vcpu, cpu) = &HYPERVISOR_shared_info->vcpu_info[cpu];
+}
+
/*
* On restore, set the vcpu placement up again.
* If it fails, then we're in a bad state, since
diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
index bc5e897..cd57801 100644
--- a/arch/x86/xen/smp.c
+++ b/arch/x86/xen/smp.c
@@ -763,16 +763,32 @@ static int xen_hvm_cpu_up(unsigned int cpu, struct task_struct *tidle)
static void xen_hvm_cpu_die(unsigned int cpu)
{
xen_cpu_die(cpu);
+ xen_teardown_vcpu_setup(cpu);
native_cpu_die(cpu);
}
#ifdef CONFIG_KEXEC
void xen_kexec_shutdown(void)
{
+ int first_cpu;
+
if (!kexec_in_progress)
return;
+ first_cpu = cpumask_first(cpu_online_mask);
+
+ gnttab_suspend();
+ xen_arch_pre_suspend();
+
+ /* Stop all CPUs except for the first one */
+ disable_nonboot_cpus();
+
xen_hvm_reset_eventchannels();
+
+ /* Bring down the IPIs, PIRQs, on the BSP. */
+ xen_raw_printk("CPU0 down.\n");
+ xen_teardown_vcpu_setup(first_cpu);
+ xen_raw_printk("CPU0 down done.\n");
}
#endif
diff --git a/arch/x86/xen/xen-ops.h b/arch/x86/xen/xen-ops.h
index d083e82..36dd380 100644
--- a/arch/x86/xen/xen-ops.h
+++ b/arch/x86/xen/xen-ops.h
@@ -53,6 +53,7 @@ void xen_init_irq_ops(void);
void xen_setup_timer(int cpu);
void xen_setup_runstate_info(int cpu);
void xen_teardown_timer(int cpu);
+void xen_teardown_vcpu_setup(int cpu);
cycle_t xen_clocksource_read(void);
void xen_setup_cpu_clockevents(void);
void __init xen_init_time_ops(void);
diff --git a/include/xen/interface/vcpu.h b/include/xen/interface/vcpu.h
index b05288c..a0a374c 100644
--- a/include/xen/interface/vcpu.h
+++ b/include/xen/interface/vcpu.h
@@ -172,4 +172,6 @@ DEFINE_GUEST_HANDLE_STRUCT(vcpu_register_vcpu_info);
/* Send an NMI to the specified VCPU. @extra_arg == NULL. */
#define VCPUOP_send_nmi 11
+
+#define VCPUOP_reset_vcpu_info 14
#endif /* __XEN_PUBLIC_VCPU_H__ */
Konrad Rzeszutek Wilk (1):
Introduce VCPUOP_reset_vcpu_info
xen/arch/x86/hvm/hvm.c | 1 +
xen/common/domain.c | 22 +++++++++++++++++++---
xen/include/public/vcpu.h | 6 ++++++
3 files changed, 26 insertions(+), 3 deletions(-)
--
1.9.3
next reply other threads:[~2014-08-06 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 13:08 Vitaly Kuznetsov [this message]
2014-08-06 13:08 ` [PATCH RFC 1/1] Introduce VCPUOP_reset_vcpu_info Vitaly Kuznetsov
2014-08-06 14:36 ` Jan Beulich
2014-08-06 14:09 ` [PATCH RFC 0/1] " Jan Beulich
2014-08-06 14:49 ` Konrad Rzeszutek Wilk
2014-08-06 14:54 ` Jan Beulich
2014-08-06 15:03 ` Konrad Rzeszutek Wilk
2014-08-06 14:51 ` Konrad Rzeszutek Wilk
2014-08-06 15:00 ` Jan Beulich
2014-08-06 15:02 ` Konrad Rzeszutek Wilk
2014-08-06 15:38 ` Jan Beulich
2014-08-06 15:03 ` Vitaly Kuznetsov
2014-08-06 15:43 ` Jan Beulich
2014-08-07 11:41 ` Vitaly Kuznetsov
2014-08-07 11:48 ` Jan Beulich
2014-08-07 11:54 ` Vitaly Kuznetsov
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=1407330502-18768-1-git-send-email-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=david.vrabel@citrix.com \
--cc=drjones@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).