From: Clark Williams <williams@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>
Subject: version 0.37 of rt-tests available
Date: Wed, 29 Apr 2009 15:50:11 -0500 [thread overview]
Message-ID: <20090429155011.09e2218f@torg> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've pushed 0.37 of the rt-tests up to my git repo at:
git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-tests.git
tarballs available at:
http://www.kernel.org/pub/linux/kernel/people/clrkwllms/rt-tests/
This version has a couple of fixes from GeunSik Lim
<geunsik.lim@samsung.com> (man page fixes and two new options for
wakeup and wakeup_rt tracing).
After seeing that we have a never-ending stream of ftrace tracing
functions and options available to us, I decided that we need a better
way to specify the tracers. So I added the --tracer option (which
accepts the name of a tracing function) and the --traceopt option
(which accepts tracing options), e.g.:
$ cyclictest -b 500 --tracer=events --traceopts=noraw --traceopts=nohex
I guess I could make traceopts take a comma separated list, but for now
it was just easier to allow multiple invocations on a command line.
I've left the other tracing options alone for now, since I'm sure people
have scripts that use them. I wouldn't mind getting rid of them in the
future though.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkn4vYoACgkQHyuj/+TTEp0eRgCgyJy7jg4o7qEGxqlwCoZRqwBq
Ct4An129sVkC7Md6fokUDpW8QOw03PPR
=HPJj
-----END PGP SIGNATURE-----
next reply other threads:[~2009-04-29 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 20:50 Clark Williams [this message]
2009-04-30 1:30 ` version 0.37 of rt-tests available GeunSik Lim
2009-04-30 5:26 ` GeunSik Lim
2009-04-30 6:52 ` Uwe Kleine-König
2009-04-30 14:10 ` Clark Williams
2009-07-02 1:57 ` [PATCH] clock_nanosleep interrupt Sven-Thorsten Dietrich
2009-07-02 14:48 ` Clark Williams
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=20090429155011.09e2218f@torg \
--to=williams@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).