[lkml]   [2013]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 06/10] dmatest: run test via debugfs
Oh, missed Cc list in the middle. Return it back and thus leave a full
message below.

On Thu, Mar 7, 2013 at 8:11 AM, Vinod Koul <> wrote:
> On Wed, Mar 06, 2013 at 05:53:20PM +0200, Andy Shevchenko wrote:
>> >> > How do you terminate a test? Esp if you have started bunch of concurent tests
>> >> > and want to terminate one of them...
>> >>
>> >> There is only one test in progress is possible.
>> > Wasnt the idea to run concurrent tests, or I read wrongly...
>> No, the idea was to run different tests sequentially from userspace
>> withou loading/unloading
>> module each time and with storage support for the results that could
>> be parsed automatically.
>> Running concurrent tests is a good feature to be in TODO list.
> I dont think anything in code prevents you from doing so. Only issue woud
> triggering bunch of tests together and killing them
> What we could build on this is
> - configuringa test but running later (so that we configure bunch of tests and
> then start them later, when ready)
> - killing a specific task

As it's not our main goal, I prefer leave in TODO this for now.
debugfs approach opens
a wide directions to get nice QA tool for DMA drivers.

> Both of these would need some 'cookie' for tests or some otehr scheme to
> identify a test

True. It could be just a idr mapping like integer # <-> test case parameters.
I think most important feature is to add the timestamps to the results.

With Best Regards,
Andy Shevchenko

 \ /
  Last update: 2013-03-07 10:21    [W:0.070 / U:1.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site