From: Daniel Wagner <wagi@monom.org>
To: John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Daniel Wagner <wagi@monom.org>
Subject: [PATCH v2 00/12] rt-tests: Add --duration argument to tests
Date: Wed, 5 Jun 2019 18:06:05 +0200 [thread overview]
Message-ID: <20190605160617.22987-1-wagi@monom.org> (raw)
An updated version of the --duration series.
It is also available from github:
https://github.com/igaw/rt-tests/tree/dw-devel
changes since v1:
- '--duration' patch splitted up
- added short option support to pi_stress
- added build warning
- added 32bit ARM 'support' to queuelat patch
Daniel Wagner (12):
rt_numa.h: Remove unused function
queuelat: Use clock syscall for ARM 32 bit
rt-utils: Move parse_time_string()
pi_stress: Allow short command line arguments
pi_stress: Rename -t command line option to -D
pmqtest: Add duration command line argument
ptsematest: Add duration command line argument
cyclicdeadline: Add duration command line argument
signaltest: Add duration command line argument
sigwaittest: Add duration command line argument
svsematest: Add duration command line argument
rt-migrate-test: Add duration command line argument
src/cyclictest/cyclictest.c | 33 --------------------------
src/cyclictest/rt_numa.h | 7 ------
src/include/rt-utils.h | 2 ++
src/lib/rt-utils.c | 34 +++++++++++++++++++++++++++
src/pi_tests/pi_stress.8 | 4 ++++
src/pi_tests/pi_stress.c | 12 +++++-----
src/pmqtest/pmqtest.8 | 5 ++++
src/pmqtest/pmqtest.c | 17 ++++++++++++--
src/ptsematest/ptsematest.8 | 5 ++++
src/ptsematest/ptsematest.c | 14 ++++++++++-
src/queuelat/queuelat.c | 31 ++++++++++++++++++++----
src/rt-migrate-test/rt-migrate-test.8 | 5 ++++
src/rt-migrate-test/rt-migrate-test.c | 12 +++++++++-
src/sched_deadline/cyclicdeadline.c | 12 +++++++++-
src/signaltest/signaltest.8 | 5 ++++
src/signaltest/signaltest.c | 14 ++++++++++-
src/sigwaittest/sigwaittest.8 | 5 ++++
src/sigwaittest/sigwaittest.c | 15 +++++++++++-
src/svsematest/svsematest.8 | 5 ++++
src/svsematest/svsematest.c | 15 +++++++++++-
20 files changed, 193 insertions(+), 59 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-05 16:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 16:06 Daniel Wagner [this message]
2019-06-05 16:06 ` [PATCH v2 01/12] rt_numa.h: Remove unused function Daniel Wagner
2019-06-13 13:48 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 02/12] queuelat: Use clock syscall for ARM 32 bit Daniel Wagner
2019-06-13 13:51 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 03/12] rt-utils: Move parse_time_string() Daniel Wagner
2019-06-13 13:57 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 04/12] pi_stress: Allow short command line arguments Daniel Wagner
2019-06-13 14:04 ` John Kacur
2019-06-16 16:29 ` Daniel Wagner
2019-06-05 16:06 ` [PATCH v2 05/12] pi_stress: Rename -t command line option to -D Daniel Wagner
2019-06-13 14:07 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 06/12] pmqtest: Add duration command line argument Daniel Wagner
2019-06-13 14:10 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 07/12] ptsematest: " Daniel Wagner
2019-06-05 16:06 ` [PATCH v2 08/12] cyclicdeadline: " Daniel Wagner
2019-06-13 14:18 ` John Kacur
2019-06-16 16:34 ` Daniel Wagner
2019-06-13 14:40 ` John Kacur
2019-06-05 16:06 ` [PATCH v2 09/12] signaltest: " Daniel Wagner
2019-06-13 19:07 ` John Kacur
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=20190605160617.22987-1-wagi@monom.org \
--to=wagi@monom.org \
--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