From: Feng Wu <feng.wu@intel.com>
To: xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, Feng Wu <feng.wu@intel.com>,
george.dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
dario.faggioli@citrix.com, jbeulich@suse.com
Subject: [PATCH v5 2/7] VMX: Properly handle pi when all the assigned devices are removed
Date: Tue, 11 Oct 2016 08:57:48 +0800 [thread overview]
Message-ID: <1476147473-30970-3-git-send-email-feng.wu@intel.com> (raw)
In-Reply-To: <1476147473-30970-1-git-send-email-feng.wu@intel.com>
This patch handles some concern cases when the last assigned device
is removed from the domain. In this case we should carefully handle
pi descriptor and the per-cpu blocking list, to make sure:
- all the PI descriptor are in the right state when next time a
devices is assigned to the domain again.
- No remaining vcpus of the domain in the per-cpu blocking list.
Here we call vmx_pi_list_remove() to remove the vCPU from the blocking list
if it is on the list. However, this could happen when vmx_vcpu_block() is
being called, hence we might incorrectly add the vCPU to the blocking list
while the last devcie is detached from the domain. Consider that the situation
can only occur when detaching the last device from the domain and it is not
a frequent operation, so we use domain_pause before that, which is considered
as an clean and maintainable solution for the situation.
Signed-off-by: Feng Wu <feng.wu@intel.com>
---
v5:
- Remove a no-op wrapper
xen/arch/x86/hvm/vmx/vmx.c | 28 ++++++++++++++++++++++++----
1 file changed, 24 insertions(+), 4 deletions(-)
diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
index 623d5bc..d210516 100644
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -163,14 +163,12 @@ static void vmx_pi_switch_to(struct vcpu *v)
pi_clear_sn(pi_desc);
}
-static void vmx_pi_do_resume(struct vcpu *v)
+static void vmx_pi_list_remove(struct vcpu *v)
{
unsigned long flags;
spinlock_t *pi_blocking_list_lock;
struct pi_desc *pi_desc = &v->arch.hvm_vmx.pi_desc;
- ASSERT(!test_bit(_VPF_blocked, &v->pause_flags));
-
/*
* Set 'NV' field back to posted_intr_vector, so the
* Posted-Interrupts can be delivered to the vCPU when
@@ -178,12 +176,12 @@ static void vmx_pi_do_resume(struct vcpu *v)
*/
write_atomic(&pi_desc->nv, posted_intr_vector);
- /* The vCPU is not on any blocking list. */
pi_blocking_list_lock = v->arch.hvm_vmx.pi_blocking.lock;
/* Prevent the compiler from eliminating the local variable.*/
smp_rmb();
+ /* The vCPU is not on any blocking list. */
if ( pi_blocking_list_lock == NULL )
return;
@@ -203,6 +201,13 @@ static void vmx_pi_do_resume(struct vcpu *v)
spin_unlock_irqrestore(pi_blocking_list_lock, flags);
}
+static void vmx_pi_do_resume(struct vcpu *v)
+{
+ ASSERT(!test_bit(_VPF_blocked, &v->pause_flags));
+
+ vmx_pi_list_remove(v);
+}
+
/* This function is called when pcidevs_lock is held */
void vmx_pi_hooks_assign(struct domain *d)
{
@@ -220,14 +225,29 @@ void vmx_pi_hooks_assign(struct domain *d)
/* This function is called when pcidevs_lock is held */
void vmx_pi_hooks_deassign(struct domain *d)
{
+ struct vcpu *v;
+
if ( !iommu_intpost || !has_hvm_container_domain(d) )
return;
ASSERT(d->arch.hvm_domain.vmx.vcpu_block);
+ /*
+ * Pausing the domain can make sure the vCPU is not
+ * running and hence calling the hooks simultaneously
+ * when deassigning the PI hooks and removing the vCPU
+ * from the blocking list.
+ */
+ domain_pause(d);
+
d->arch.hvm_domain.vmx.vcpu_block = NULL;
d->arch.hvm_domain.vmx.pi_do_resume = NULL;
d->arch.hvm_domain.vmx.pi_switch_from = NULL;
+
+ for_each_vcpu ( d, v )
+ vmx_pi_list_remove(v);
+
+ domain_unpause(d);
}
static int vmx_domain_initialise(struct domain *d)
--
2.1.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-11 0:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 0:57 [PATCH v5 0/7] VMX: Properly handle pi descriptor and per-cpu blocking list Feng Wu
2016-10-11 0:57 ` [PATCH v5 1/7] VMX: Statically assign two PI hooks Feng Wu
2016-10-11 8:11 ` Tian, Kevin
2016-10-12 13:25 ` Jan Beulich
2016-10-11 0:57 ` Feng Wu [this message]
2016-10-11 8:20 ` [PATCH v5 2/7] VMX: Properly handle pi when all the assigned devices are removed Tian, Kevin
2016-10-11 0:57 ` [PATCH v5 3/7] VMX: Cleanup PI per-cpu blocking list when vcpu is destroyed Feng Wu
2016-10-11 0:57 ` [PATCH v5 4/7] VMX: Make sure PI is in proper state before install the hooks Feng Wu
2016-10-12 13:45 ` Jan Beulich
2016-10-17 6:26 ` Wu, Feng
2016-10-24 7:22 ` Jan Beulich
2016-10-24 7:45 ` Wu, Feng
2016-10-24 7:59 ` Jan Beulich
2016-10-11 0:57 ` [PATCH v5 5/7] VT-d: No need to set irq affinity for posted format IRTE Feng Wu
2016-10-12 13:56 ` Jan Beulich
2016-10-17 7:02 ` Wu, Feng
2016-10-24 7:27 ` Jan Beulich
2016-10-24 8:57 ` Wu, Feng
2016-10-24 9:53 ` Jan Beulich
2016-10-24 10:18 ` Wu, Feng
2016-10-24 10:57 ` Jan Beulich
2016-10-24 11:10 ` Wu, Feng
2016-10-24 11:31 ` Jan Beulich
2016-10-25 1:04 ` Wu, Feng
2016-10-25 5:57 ` Tian, Kevin
2016-10-25 8:09 ` Jan Beulich
2016-10-26 9:12 ` Wu, Feng
2016-10-26 9:51 ` Jan Beulich
2016-10-11 0:57 ` [PATCH v5 6/7] VT-d: Some cleanups Feng Wu
2016-10-12 14:01 ` Jan Beulich
2016-10-11 0:57 ` [PATCH v5 7/7] VMX: Fixup PI descriptor when cpu is offline Feng Wu
2016-10-11 8:38 ` Tian, Kevin
2016-10-11 11:46 ` Wu, Feng
2016-10-11 8:08 ` [PATCH v5 0/7] VMX: Properly handle pi descriptor and per-cpu blocking list Tian, Kevin
2016-10-11 8:11 ` Wu, Feng
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=1476147473-30970-3-git-send-email-feng.wu@intel.com \
--to=feng.wu@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.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).