xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Feng Wu <feng.wu@intel.com>, Kevin Tian <kevin.tian@intel.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v15 0/3] VT-d Device-TLB flush issue
Date: Fri, 08 Jul 2016 00:52:28 -0600	[thread overview]
Message-ID: <577F69CC02000078000FC772@prv-mh.provo.novell.com> (raw)
In-Reply-To: <577F66BC02000078000FC743@prv-mh.provo.novell.com>

>>> On 08.07.16 at 08:39, <JBeulich@suse.com> 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

I should probably have said somewhere that obviously I didn't test
this for the actual ATS case, as I don't have access to any suitable
device. Therefore, alongside the necessary ack-s, it would be nice
if we could also get a Tested-by from someone who does have an
ATS device.


Xen-devel mailing list

  parent reply	other threads:[~2016-07-08  6:52 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 ` Jan Beulich [this message]
2016-07-13  3:05   ` [PATCH v15 0/3] VT-d Device-TLB flush issue Xu, Quan
2016-07-15  9:59 ` Andrew Cooper

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577F69CC02000078000FC772@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=feng.wu@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xenproject.org \


* 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).