Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace threshold
From: John Kacur
Date: Wed May 04 2016 - 09:49:18 EST
On Wed, 4 May 2016, Luiz Capitulino wrote:
> On Tue, 3 May 2016 15:28:39 -0500
> Clark Williams <williams@xxxxxxxxxx> wrote:
>
> > The intent is to be able to do something like this:
> >
> > trace-cmd start -e all -p function
> > rteval --duration=12h --cyclictest-breaktrace=150
> > trace-cmd extract
>
> Ah, ok, I get it now. This makes sense.
>
> I think I'd refactor the code opening tracing_on to its own
> function so that we avoid the duplicate code in setup_tracer(),
> but in any case:
>
> Reviewed-by: Luiz Capitulino <lcapitulino@xxxxxxxxxx>
> --
Sorry, resending with a sane mailer
I don't see a better solution for now, so
adding Luiz Reviewed by
Signed-off-by: John Kacur <jkacur@xxxxxxxxxx>
and pushed to devel