From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: "Wu, Feng" <feng.wu@intel.com>
Subject: Re: [PATCH v15 3/3] VT-d: fix Device-TLB flush timeout issue
Date: Mon, 11 Jul 2016 03:10:20 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D15F8F7743@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <577F685702000078000FC756@prv-mh.provo.novell.com>
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Friday, July 08, 2016 2:46 PM
>
> From: Quan Xu <quan.xu@intel.com>
>
> 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).
>
> Signed-off-by: Quan Xu <quan.xu@intel.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> v15: Re-base on heavily changed patch 1. Call disable_ats_device() and
> domain_crash() from iommu_dev_iotlb_flush_timeout() and move the
> function to passthrough/pci.c to fix the ARM build. As a result of
> calling disable_ats_device() also use list_for_each_entry_safe()
> in dev_invalidate_iotlb().
>
Acked-by: Kevin Tian <kevin.tian@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-11 3:10 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 [this message]
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
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=AADFC41AFE54684AB9EE6CBC0274A5D15F8F7743@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=JBeulich@suse.com \
--cc=feng.wu@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).