From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Vinod Koul <vinod.koul@intel.com>, "djbw@fb.com" <djbw@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.jf.intel.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>
Subject: Re: dmatest regression in 3.10-rc1
Date: Tue, 21 May 2013 15:31:00 +0300 [thread overview]
Message-ID: <1369139460.29283.147.camel@smile> (raw)
In-Reply-To: <20130520095857.GI31359@mudshark.cambridge.arm.com>
On Mon, 2013-05-20 at 10:58 +0100, Will Deacon wrote:
> Sure. They way I trigger it is to unload the module whilst the DMA is
> ongoing (I'm using a software model, so I can make the DMA nice and slow --
> I guess you could try using some large buffers).
Thank you for the script. It looks like I managed to reproduce it with
help of your script. I'm about to send the patch. I will appreciate to
collect a Tested-by tags in case it solves the issue.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2013-05-21 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 15:28 dmatest regression in 3.10-rc1 Will Deacon
2013-05-16 15:35 ` Will Deacon
2013-05-17 12:34 ` Vinod Koul
2013-05-17 14:18 ` Will Deacon
2013-05-20 7:52 ` Andy Shevchenko
2013-05-20 9:58 ` Will Deacon
2013-05-21 12:31 ` Andy Shevchenko [this message]
2013-05-21 12:33 ` [PATCH] dmatest: abort transfers immediately when asked for Andy Shevchenko
2013-05-21 15:11 ` Will Deacon
2013-05-21 17:24 ` Andy Shevchenko
2013-05-22 12:41 ` Will Deacon
2013-05-22 13:26 ` Andy Shevchenko
2013-05-23 10:09 ` Vinod Koul
2013-05-23 10:51 ` Andy Shevchenko
2013-05-23 10:22 ` Vinod Koul
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=1369139460.29283.147.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=djbw@fb.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.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