From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH v15 0/3] VT-d Device-TLB flush issue
Date: Fri, 15 Jul 2016 10:59:58 +0100 [thread overview]
Message-ID: <e17ab3e0-f1b5-8bdd-c2a9-43e4ea929533@citrix.com> (raw)
In-Reply-To: <577F66BC02000078000FC743@prv-mh.provo.novell.com>
On 08/07/16 07:39, Jan Beulich wrote:
> From: Quan Xu <quan.xu@intel.com>
>
> these patches fix current timeout concern and also allow limited ATS support.
>
> these patches are the rest ones:
> 1. move the domain crash logic up to the generic IOMMU layer
>
> 2. If Device-TLB flush timed out, we hide the target ATS device
> immediately. By hiding the device, we make sure it can't be
> assigned to any domain any longer (see device_assigned).
>
> Quan Xu (3):
> IOMMU/ATS: use a struct pci_dev * instead of SBDF
> IOMMU: add domain crash logic
> VT-d: fix Device-TLB flush timeout issue
Committed, thanks.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-15 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 6:39 [PATCH v15 0/3] VT-d Device-TLB flush issue Jan Beulich
2016-07-08 6:44 ` [PATCH v15 1/3] IOMMU/ATS: use a struct pci_dev * instead of SBDF Jan Beulich
2016-07-11 3:07 ` Tian, Kevin
2016-07-08 6:45 ` [PATCH v15 2/3] IOMMU: add domain crash logic Jan Beulich
2016-07-08 6:46 ` [PATCH v15 3/3] VT-d: fix Device-TLB flush timeout issue Jan Beulich
2016-07-11 3:10 ` Tian, Kevin
2016-07-08 6:52 ` [PATCH v15 0/3] VT-d Device-TLB flush issue Jan Beulich
2016-07-13 3:05 ` Xu, Quan
2016-07-15 9:59 ` Andrew Cooper [this message]
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=e17ab3e0-f1b5-8bdd-c2a9-43e4ea929533@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@intel.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).