From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
suravee.suthikulpanit@amd.com
Cc: LiangX Z Li <liangx.z.li@intel.com>,
Yang ZZhang <yang.z.zhang@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Eddie Dong <eddie.dong@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VT-d flush timeout
Date: Thu, 25 Sep 2014 11:56:18 +0100 [thread overview]
Message-ID: <5423F4D2.60605@citrix.com> (raw)
In-Reply-To: <542410A90200007800038E3B@mail.emea.novell.com>
On 25/09/14 11:55, Jan Beulich wrote:
>>>> On 25.09.14 at 12:44, <andrew.cooper3@citrix.com> wrote:
>> The AMD code will wait for a period of time for the COMMAND_WAIT to
>> start, but not panic() on a timeout.
>>
>> By my reading of the code, amd_iommu_flush_iotlb() can complete without
>> confirming that the iotlbs have actually been flushed, and all that is
>> left behind is an AMD_IOMMU_DEBUG() message.
> Now that you say this I recall having stumbled across this questionable
> behavior in the past (and perhaps even more than once). Certainly
> something for our AMD IOMMU maintainers to look into...
>
> Jan
>
Agreed, although for now I think it is safer to leave ATS disabled.
~Andrew
next prev parent reply other threads:[~2014-09-25 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 2:01 VT-d flush timeout Zhang, Yang Z
2014-08-18 9:47 ` Andrew Cooper
2014-08-18 12:48 ` Jan Beulich
2014-08-19 1:34 ` Zhang, Yang Z
2014-08-19 13:02 ` Jan Beulich
2014-08-21 3:16 ` Zhang, Yang Z
2014-08-22 7:33 ` Jan Beulich
2014-08-22 7:49 ` Zhang, Yang Z
2014-08-22 7:58 ` Jan Beulich
2014-08-22 8:05 ` Zhang, Yang Z
2014-08-25 17:21 ` Dugger, Donald D
2014-09-25 1:02 ` Dong, Eddie
2014-09-25 8:55 ` Jan Beulich
2014-09-25 10:44 ` Andrew Cooper
2014-09-25 10:55 ` Jan Beulich
2014-09-25 10:56 ` Andrew Cooper [this message]
2014-09-25 11:48 ` Jan Beulich
2014-09-25 21:21 ` Tian, Kevin
2014-09-25 23:23 ` Dong, Eddie
2014-09-26 1:07 ` Zhang, Yang Z
2014-09-26 6:30 ` Jan Beulich
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=5423F4D2.60605@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=eddie.dong@intel.com \
--cc=kevin.tian@intel.com \
--cc=liangx.z.li@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/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).