From: "Xu, Quan" <quan.xu@intel.com>
To: xen-devel@lists.xen.org
Cc: dario.faggioli@citrix.com, Quan Xu <quan.xu@intel.com>
Subject: [PATCH v9 0/3] Check VT-d Device-TLB flush error
Date: Fri, 17 Jun 2016 11:37:22 +0800 [thread overview]
Message-ID: <1466134645-50852-1-git-send-email-quan.xu@intel.com> (raw)
From: Quan Xu <quan.xu@intel.com>
This patch set is a prereq patch set for Patch:'VT-d Device-TLB flush issue'.
While IOMMU Device-TLB flush timed out, xen calls panic() at present. However the existing panic()
is going to be eliminated, so we must propagate the IOMMU Device-TLB flush error up to the call trees.
This patch set is also based on the discussion of 'abstract model of IOMMU unmaping/mapping failures'.
---
Quan Xu (3):
vt-d: fix the IOMMU flush issue
vt-d: propagate the IOMMU Device-TLB flush error up to ME phantom
functions
vt-d: add __must_check annotation to IOMMU flush pointers and handlers
xen/drivers/passthrough/vtd/extern.h | 3 +-
xen/drivers/passthrough/vtd/iommu.c | 184 +++++++++++++++++++++++------------
xen/drivers/passthrough/vtd/iommu.h | 11 ++-
xen/drivers/passthrough/vtd/qinval.c | 14 +--
xen/drivers/passthrough/vtd/quirks.c | 27 +++--
5 files changed, 153 insertions(+), 86 deletions(-)
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-17 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 3:37 Xu, Quan [this message]
2016-06-17 3:37 ` [PATCH v9 1/3] vt-d: fix the IOMMU flush issue Xu, Quan
2016-06-21 13:25 ` Jan Beulich
2016-06-22 3:07 ` Xu, Quan
2016-06-17 3:37 ` [PATCH v9 2/3] vt-d: propagate the IOMMU Device-TLB flush error up to ME phantom functions Xu, Quan
2016-06-17 3:37 ` [PATCH v9 3/3] vt-d: add __must_check annotation to IOMMU flush pointers and handlers Xu, Quan
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=1466134645-50852-1-git-send-email-quan.xu@intel.com \
--to=quan.xu@intel.com \
--cc=dario.faggioli@citrix.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).