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 <[email protected]> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
