From: "Xu, Quan" <quan.xu@intel.com>
To: Jan Beulich <JBeulich@suse.com>, "Wu, Feng" <feng.wu@intel.com>,
"Tian, Kevin" <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: Wed, 13 Jul 2016 03:05:37 +0000 [thread overview]
Message-ID: <945CA011AD5F084CBEA3E851C0AB28894B8FD7EA@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <577F69CC02000078000FC772@prv-mh.provo.novell.com>
On July 08, 2016 2:52 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >>> 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.
>
(today I just come back to return my laptop and while test it) thanks for your work and education :):)...
Tested-by: Quan Xu <quan.xu@intel.com>
Quan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-13 3:05 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 [this message]
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:
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=945CA011AD5F084CBEA3E851C0AB28894B8FD7EA@SHSMSX101.ccr.corp.intel.com \
--to=quan.xu@intel.com \
--cc=JBeulich@suse.com \
--cc=feng.wu@intel.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).