From: Luiz Capitulino <lcapitulino@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH][rt-tests] cyclictest: Make the tracemark option imply notrace
Date: Thu, 24 Mar 2016 10:52:55 -0400 [thread overview]
Message-ID: <20160324105255.48459b11@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1603241543150.8641@riemann>
On Thu, 24 Mar 2016 15:44:39 +0100 (CET)
John Kacur <jkacur@redhat.com> wrote:
> From 6b663b39fc5dc7c4e9c78ab22012f07490e53145 Mon Sep 17 00:00:00 2001
> From: John Kacur <jkacur@redhat.com>
> Date: Thu, 24 Mar 2016 15:40:03 +0100
> Subject: [PATCH] cyclictest: Make the tracemark option imply notrace
>
> The new --tracemark option can be used to run cyclictest under
> trace-cmd.
>
> This means we don't want cyclictest's built-in tracing to be used, so
> this option is only compatible with --notrace.
>
> Therefore turn --notrace on if --tracemark is invoked even if the user
> doesn't explicitly request this.
I'm not necessarily against this, but at the same time I think
I prefer options doing only one thing.
>
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
> src/cyclictest/cyclictest.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
> index 4844dfaf33a6..158bceda1204 100644
> --- a/src/cyclictest/cyclictest.c
> +++ b/src/cyclictest/cyclictest.c
> @@ -1765,6 +1765,7 @@ static void process_options (int argc, char *argv[], int max_cpus)
> #endif
> break;
> case OPT_TRACEMARK:
> + notrace = 1; /* using --tracemark implies --notrace */
> trace_marker = 1; break;
> }
> }
next prev parent reply other threads:[~2016-03-24 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:44 [PATCH][rt-tests] cyclictest: Make the tracemark option imply notrace John Kacur
2016-03-24 14:52 ` Luiz Capitulino [this message]
2016-03-24 15:24 ` John Kacur
2016-03-24 15:57 ` Mats Karrman
2016-03-24 16:07 ` Luiz Capitulino
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=20160324105255.48459b11@redhat.com \
--to=lcapitulino@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).