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 v4 0/6] VMX: Properly handle pi descriptor and per-cpu blocking list
Date: Wed, 21 Sep 2016 10:37:44 +0800 [thread overview]
Message-ID: <1474425470-3629-1-git-send-email-feng.wu@intel.com> (raw)
The current VT-d PI related code may operate incorrectly in the
following scenarios:
1. When the last assigned device is dettached from the domain, all
the PI related hooks are removed then, however, the vCPU can be
blocked, switched to another pCPU, etc, all without the aware of
PI. After the next time we attach another device to the domain,
which makes the PI realted hooks avaliable again, the status
of the pi descriptor is not true. Beside that, the blocking vcpu
may still remain in the per-cpu blocking in this case. Patch [1/6]
and [2/6] handle this.
2. After the domain is destroyed, the the blocking vcpu may also
remain in the per-cpu blocking. Handled in patch [3/6].
3. When IRTE is in posted mode, we don't need to set the irq
affinity for it, since the destination of these interrupts is
vCPU and the vCPU affinity is set during vCPU scheduling. Patch
[5/6] handles this.
4. When a pCPU is unplugged, and there might be vCPUs on its
list. Since the pCPU is offline, those vCPUs might not be woken
up again. [6/6] addresses it.
Feng Wu (6):
VMX: Statically assign two PI hooks
VMX: Properly handle pi when all the assigned devices are removed
VMX: Cleanup PI per-cpu blocking list when vcpu is destroyed
VMX: Make sure PI is in proper state before install the hooks
VT-d: No need to set irq affinity for posted format IRTE
VMX: Fixup PI descritpor when cpu is offline
xen/arch/x86/hvm/vmx/vmcs.c | 14 ++---
xen/arch/x86/hvm/vmx/vmx.c | 105 ++++++++++++++++++++++++++++++---
xen/drivers/passthrough/vtd/intremap.c | 9 ++-
xen/include/asm-x86/hvm/vmx/vmx.h | 1 +
4 files changed, 111 insertions(+), 18 deletions(-)
--
2.1.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-09-21 2:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 2:37 Feng Wu [this message]
2016-09-21 2:37 ` [PATCH v4 1/6] VMX: Statically assign two PI hooks Feng Wu
2016-09-26 11:37 ` Jan Beulich
2016-09-26 12:09 ` Jan Beulich
2016-09-28 6:48 ` Wu, Feng
2016-09-28 9:38 ` Jan Beulich
2016-10-09 8:30 ` Wu, Feng
2016-10-10 7:26 ` Jan Beulich
2016-09-21 2:37 ` [PATCH v4 2/6] VMX: Properly handle pi when all the assigned devices are removed Feng Wu
2016-09-26 11:46 ` Jan Beulich
2016-09-28 6:50 ` Wu, Feng
2016-09-28 9:52 ` Jan Beulich
2016-09-29 3:08 ` Wu, Feng
2016-09-21 2:37 ` [PATCH v4 3/6] VMX: Cleanup PI per-cpu blocking list when vcpu is destroyed Feng Wu
2016-09-21 2:37 ` [PATCH v4 4/6] VMX: Make sure PI is in proper state before install the hooks Feng Wu
2016-09-26 12:45 ` Jan Beulich
2016-09-28 6:50 ` Wu, Feng
2016-09-21 2:37 ` [PATCH v4 5/6] VT-d: No need to set irq affinity for posted format IRTE Feng Wu
2016-09-26 12:58 ` Jan Beulich
2016-09-28 6:51 ` Wu, Feng
2016-09-28 9:58 ` Jan Beulich
2016-10-09 5:35 ` Wu, Feng
2016-10-10 7:02 ` Jan Beulich
2016-10-10 22:55 ` Wu, Feng
2016-09-21 2:37 ` [PATCH v4 6/6] VMX: Fixup PI descritpor when cpu is offline Feng Wu
2016-09-26 13:03 ` Jan Beulich
2016-09-28 6:53 ` 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=1474425470-3629-1-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).