From: "Jan Beulich" <JBeulich@suse.com>
To: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Eddie Dong <eddie.dong@intel.com>,
Yang Z Zhang <yang.z.zhang@intel.com>
Cc: LiangX Z Li <liangx.z.li@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VT-d flush timeout
Date: Fri, 26 Sep 2014 07:30:55 +0100 [thread overview]
Message-ID: <5425243F0200007800039658@mail.emea.novell.com> (raw)
In-Reply-To: <A12AC9D104E08D47BAF23C492F83C53B2594E023@SHSMSX104.ccr.corp.intel.com>
>>> On 26.09.14 at 01:23, <eddie.dong@intel.com> wrote:
>> >>
>> >
>> > Giving this path of long time wait-loop only happens at the case when
>> > the hardware fails, I don't care if it enters panic in 1 seconds or in
>> > 10ms seconds. But the software compatibility (for all existing
>> > platforms and potential future platforms) is much more important.
>>
>> I agree for the paths leading to a panic(). But there's one such case where
> it
>> doesn't: snb_vtd_ops_preamble().
>>
>
> For some reason, it is using a same MAGIC TIMEOUT value with VTd flush
> timeout.
> They are actually different and this one is used to prevent the IGD to enter
> RC6 state :)
>
> Whether the IGD enters RC6 state in 1second is another story, it doesn't
> indicate the
> hardware is bad, like the VTD flush timeout indicates. So it is not
> necessary to enter panic.
>
> Maybe we should cook a patch to use different TIMEOUT MACRO, though they are
> 1second in both cases.
If it needs to stay 1 second, more than just introducing a separate
macro should be done. If the value can be reduced to a couple of
milliseconds, keeping the code as is with just the new macro put in
place would be fine.
Jan
prev parent reply other threads:[~2014-09-26 6:30 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
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 [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=5425243F0200007800039658@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=kevin.tian@intel.com \
--cc=liangx.z.li@intel.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).