mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jiang, Dave" <dave.jiang@intel.com>
To: "der.herr@hofr.at" <der.herr@hofr.at>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rashika.kheria@gmail.com" <rashika.kheria@gmail.com>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	"prarit@redhat.com" <prarit@redhat.com>,
	"josh@joshtriplett.org" <josh@joshtriplett.org>
Subject: Re: [PATCH] ioat: fail self-test if wait_for_completion times out
Date: Tue, 6 Jan 2015 15:38:02 +0000	[thread overview]
Message-ID: <1420558682.62574.2.camel@djiang5-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20150106004246.GA31803@opentech.at>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3556 bytes --]




On Tue, 2015-01-06 at 00:42 +0000, Nicholas Mc Guire wrote:
> On Mon, 05 Jan 2015, Jiang, Dave wrote:
> 
> > 
> > 
> > 
> > On Sun, 2014-12-28 at 10:37 +0000, Nicholas Mc Guire wrote:
> > > wait_for_completion_timeout reaching timeout was being ignored,
> > > fail the self-test if timeout condition occurs.
> > > 
> > > Not sure about the indentations used (CodingStyle:Chapter 2)
> > > 
> > > this was only compile tested with
> > > x86_64_defconfig + CONFIG_DMA_ENGINE=y + CONFIG_INTEL_IOATDMA=y
> > > 
> > > patch is against linux-next 3.19.0-rc1 -next-20141226
> > > 
> > > Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
> > > ---
> > >  drivers/dma/ioat/dma_v3.c |    9 ++++++---
> > >  1 file changed, 6 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/drivers/dma/ioat/dma_v3.c b/drivers/dma/ioat/dma_v3.c
> > > index be307182..0659215 100644
> > > --- a/drivers/dma/ioat/dma_v3.c
> > > +++ b/drivers/dma/ioat/dma_v3.c
> > > @@ -1311,7 +1311,8 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
> > > 
> > >  	tmo = wait_for_completion_timeout(&cmp, msecs_to_jiffies(3000));
> > > 
> > > -	if (dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
> > > +	if (tmo == 0 || dma->device_tx_status(dma_chan, cookie, NULL)
> > > +			!= DMA_COMPLETE) {
> > >  		dev_err(dev, "Self-test xor timed out\n");
> > >  		err = -ENODEV;
> > >  		goto dma_unmap;
> > > @@ -1377,7 +1378,8 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
> > > 
> > >  	tmo = wait_for_completion_timeout(&cmp, msecs_to_jiffies(3000));
> > > 
> > > -	if (dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
> > > +	if (tmo == 0 || dma->device_tx_status(dma_chan, cookie, NULL)
> > > +			!= DMA_COMPLETE) {
> > 
> > Can you please do: 
> > +	if (tmo == 0 ||
> > +	    dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
> 
> Documentation/CodingStyle:Chapter 2
> 
> "Statements longer than 80 columns will be broken into sensible chunks, unless
> exceeding 80 columns significantly increases readability and does not hide
> information. Descendants are always substantially shorter than the parent and
> are placed substantially to the right. The same applies to function headers..."
> 
> am I misreading the CodingStyle here ?

I'm not sure what the issue is here.... What I proposed is still the
same length as the original code. And what I suggested complies with the
existing coding style that's already there.

> 
> > 
> > Otherwise it looks good. Although I've never hit that error condition either. 
> > 
> > >  		dev_err(dev, "Self-test validate timed out\n");
> > >  		err = -ENODEV;
> > >  		goto dma_unmap;
> > > @@ -1429,7 +1431,8 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
> > > 
> > >  	tmo = wait_for_completion_timeout(&cmp, msecs_to_jiffies(3000));
> > > 
> > > -	if (dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
> > > +	if (tmo == 0 || dma->device_tx_status(dma_chan, cookie, NULL)
> > > +			!= DMA_COMPLETE) {
> > >  		dev_err(dev, "Self-test 2nd validate timed out\n");
> > >  		err = -ENODEV;
> > >  		goto dma_unmap;
> > > --
> > > 1.7.10.4
> > > 
> 
> thx!
> hofrat
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2015-01-06 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 10:37 Nicholas Mc Guire
2015-01-02 11:47 ` Prarit Bhargava
2015-01-05 16:51 ` Jiang, Dave
2015-01-06  0:42   ` Nicholas Mc Guire
2015-01-06 15:38     ` Jiang, Dave [this message]
2015-01-07 12:46       ` Prarit Bhargava
2015-01-07 13:09         ` Nicholas Mc Guire
2015-01-07 16:22           ` Jiang, Dave

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=1420558682.62574.2.camel@djiang5-desk2.amr.corp.intel.com \
    --to=dave.jiang@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=der.herr@hofr.at \
    --cc=dmaengine@vger.kernel.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rashika.kheria@gmail.com \
    --cc=vinod.koul@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

all inboxes | Powered by JetHome®