All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com
Subject: Re: [PATCH 0/4] cyclictest: improve running under trace-cmd
Date: Thu, 17 Mar 2016 09:48:43 -0400	[thread overview]
Message-ID: <20160317094843.5e1f4b49@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1603162336430.16977@riemann>

On Wed, 16 Mar 2016 23:37:21 +0100 (CET)
John Kacur <jkacur@redhat.com> wrote:

> 
> 
> On Wed, 16 Mar 2016, Luiz Capitulino wrote:
> 
> > On Thu, 25 Feb 2016 11:29:13 -0500
> > Luiz Capitulino <lcapitulino@redhat.com> wrote:
> > 
> > > 
> > > This is just a repost of my RFC posting with no changes.
> > > I have tested it a bit more and I think it's good
> > > for inclusion.
> > 
> > ping?
> > 
> > > 
> > > Original intro:
> > > 
> > > In short, this series allows you to run cyclictest under
> > > trace-cmd and still get trace marks when the latency
> > > specified with -b is execeded. More details in patch 4/4.
> > > 
> > > This series is RFC because I'm not completely sure this
> > > is the right thing to do. I'm wondering if we shouldn't
> > > ditch all tracing support from cyclictest...
> > > 
> > > Luiz Capitulino (4):
> > >   cyclictest: tracing(): check for notrace
> > >   cyclictest: move debugfs init code to its own function
> > >   cyclictest: move tracemark_fd handling to its own function
> > >   cyclictest: add --tracemark option
> > > 
> > >  src/cyclictest/cyclictest.c | 62 ++++++++++++++++++++++++++++++++++-----------
> > >  1 file changed, 47 insertions(+), 15 deletions(-)
> > > 
> > 
> > --
> 
> I'll have a closer look tomorrow, but these look okay.

There's a small conflict due to the older repo I was using. I'll
rebase it, re-test and re-post.

      reply	other threads:[~2016-03-17 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 16:29 [PATCH 0/4] cyclictest: improve running under trace-cmd Luiz Capitulino
2016-02-25 16:29 ` [PATCH 1/4] cyclictest: tracing(): check for notrace Luiz Capitulino
2016-02-25 16:29 ` [PATCH 2/4] cyclictest: move debugfs init code to its own function Luiz Capitulino
2016-02-25 16:29 ` [PATCH 3/4] cyclictest: move tracemark_fd handling " Luiz Capitulino
2016-02-25 16:29 ` [PATCH 4/4] cyclictest: add --tracemark option Luiz Capitulino
2016-03-16 21:23 ` [PATCH 0/4] cyclictest: improve running under trace-cmd Luiz Capitulino
2016-03-16 22:37   ` John Kacur
2016-03-17 13:48     ` Luiz Capitulino [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160317094843.5e1f4b49@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.