Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1394289

Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace threshold

From Luiz Capitulino <lcapitulino@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace threshold
Date 2016-05-04 15:30 +0200
Message-ID <rv52i-4BT-27@gated-at.bofh.it> (permalink)
References <ruMVI-4wA-21@gated-at.bofh.it> <ruOEa-5Zc-13@gated-at.bofh.it> <ruP7c-6xa-19@gated-at.bofh.it>
Organization Red Hat

Show all headers | View raw

On Tue, 3 May 2016 15:28:39 -0500
Clark Williams <williams@redhat.com> 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@redhat.com>

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH] cyclictest: stop any tracing after hitting a breaktrace  threshold Clark Williams <williams@redhat.com> - 2016-05-03 20:10 +0200
  Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace  threshold Luiz Capitulino <lcapitulino@redhat.com> - 2016-05-03 22:00 +0200
    Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace  threshold Clark Williams <williams@redhat.com> - 2016-05-03 22:30 +0200
      Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace  threshold Luiz Capitulino <lcapitulino@redhat.com> - 2016-05-04 15:30 +0200
        Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace  threshold John Kacur <jkacur@redhat.com> - 2016-05-04 15:50 +0200

csiph-web