All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xu, Quan" <quan.xu@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "tim@xen.org" <tim@xen.org>, "Tian, Kevin" <kevin.tian@intel.com>,
	"Wu, Feng" <feng.wu@intel.com>,
	"george.dunlap@eu.citrix.com" <george.dunlap@eu.citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"keir@xen.org" <keir@xen.org>
Subject: Re: [PATCH v2 1/2] VT-d: Reduce spin timeout to 1ms, which can be boot-time changed.
Date: Fri, 11 Dec 2015 14:03:49 +0000	[thread overview]
Message-ID: <945CA011AD5F084CBEA3E851C0AB28894AE598AD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <566AAD0902000078000BE8C5@prv-mh.provo.novell.com>

> On 11.12.2015 at 6:01pm, <JBeulich@suse.com> wrote:
> >>> On 10.12.15 at 10:33, <quan.xu@intel.com> wrote:
> > @@ -167,10 +172,12 @@ static int queue_invalidate_wait(struct iommu
> *iommu,
> >          start_time = NOW();
> >          while ( poll_slot != QINVAL_STAT_DONE )
> >          {
> > -            if ( NOW() > (start_time + DMAR_OPERATION_TIMEOUT) )
> > +            if ( NOW() > (start_time + IOMMU_QI_TIMEOUT) )
> >              {
> >                  print_qi_regs(iommu);
> > -                panic("queue invalidate wait descriptor was not
> executed");
> > +                dprintk(XENLOG_WARNING VTDPREFIX,
> > +                        "Queue invalidate wait descriptor was
> timeout.\n");
> > +                return -ETIMEDOUT;
> >              }
> 
> I don't see such a change be valid without making sure callers actually honor
> errors. For example, no caller of iommu_flush_iec_{global,index}() cares to
> check. And not even your second patch addresses this (i.e.
> it's also not just bad patch ordering).
> 
> If you require errors to be dealt with (and you do here), make use of
> __must_check all the way up the call trees.
> 

ok, I will make use of __must_check all the way up the call trees in v3.

Quan

  reply	other threads:[~2015-12-11 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10  9:33 [PATCH v2 0/2] VT-d flush issue Quan Xu
2015-12-10  9:33 ` [PATCH v2 1/2] VT-d: Reduce spin timeout to 1ms, which can be boot-time changed Quan Xu
2015-12-10 19:03   ` Andrew Cooper
2015-12-11  2:09     ` Xu, Quan
2015-12-11  7:00       ` Tian, Kevin
2015-12-11  7:29         ` Xu, Quan
2015-12-11  8:37       ` Andrew Cooper
2015-12-11  8:45         ` Xu, Quan
2015-12-11 10:01   ` Jan Beulich
2015-12-11 14:03     ` Xu, Quan [this message]
2015-12-12  9:03     ` Xu, Quan
2015-12-14  8:18       ` Jan Beulich
2015-12-14  8:31         ` Xu, Quan
2015-12-14  8:49           ` Jan Beulich
2015-12-10  9:33 ` [PATCH v2 2/2] VT-d: Fix vt-d flush timeout issue Quan Xu
2015-12-10 19:05   ` Andrew Cooper
2015-12-11  5:37     ` Xu, Quan
2015-12-11  8:38       ` Andrew Cooper
2015-12-11  8:42         ` Xu, Quan
2015-12-11  7:27   ` Tian, Kevin
2015-12-11  8:01     ` Xu, Quan
2015-12-11 10:04       ` Jan Beulich
2015-12-11 14:00         ` Xu, Quan
2015-12-11 14:12           ` Xu, Quan

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=945CA011AD5F084CBEA3E851C0AB28894AE598AD@SHSMSX103.ccr.corp.intel.com \
    --to=quan.xu@intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=feng.wu@intel.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.