On Wed, 2010-09-08 at 14:13 -0700, Gregory Smith wrote: > Add a docstring so that test_importer picks up ftrace. > > SRSLY? UGH. > > * We shouldn't have these requirements at all and should specify test > and profiler metadata in its own structured format file in the same > directory...
Hey Greg, I was looking at this and realized that we don't have an ftrace profiler upstream... This is something from your internal tree, so I'll mark it as 'Not applicable' on patchwork. In case it's possible, what about send this profiler upstream? Thanks! P.S: About control file requirements, your suggestion is good. Maybe we can talk more about that on the mailing list, with an RFC. > Signed-off-by: Gregory Smith <[email protected]> > > --- autotest/client/profilers/ftrace/ftrace.py 2010-09-07 > 14:02:55.000000000 -0700 > +++ autotest/client/profilers/ftrace/ftrace.py 2010-09-08 > 14:03:25.000000000 -0700 > @@ -1,3 +1,7 @@ > +""" > +An Autotest profiler to turn on ftrace during a test. > +""" > + > import os > import signal > import subprocess > _______________________________________________ > Autotest mailing list > [email protected] > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
