From: John Kacur <jkacur@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>,
Daniel Wagner <dwagner@suse.de>, Mike Galbraith <efault@gmx.de>,
Kurt Kanzenbach <kurt@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: [ANNOUNCE] rt-tests-2.1
Date: Tue, 29 Jun 2021 23:23:30 -0400 [thread overview]
Message-ID: <20210630032330.17973-1-jkacur@redhat.com> (raw)
This release just contains the fix for the problem reported and
investigated by Mike Galbraith. Thanks Mike
The solution was to move the get_timestamp() call to the ramp up phase
before the actual benchmark starts.
Bug reports, testing, patches are always appreciated.
Enjoy!
Clone
git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
https://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
https://kernel.googlesource.com/pub/scm/utils/rt-tests/rt-tests.git
Branch: main
Tag: v2.1
Tarballs are available here:
https://kernel.org/pub/linux/utils/rt-tests
Older version tarballs are available here:
https://kernel.org/pub/linux/utils/rt-tests/older
Daniel Wagner (2):
rt-utils: Call get_timestmap() in rt_init()
rt-utils: Remove empty rt_test_start()
John Kacur (1):
rt-tests: Change VERSION to 2.1
Makefile | 2 +-
src/cyclictest/cyclictest.c | 1 -
src/include/rt-utils.h | 2 --
src/lib/rt-utils.c | 29 ++++++++++++---------------
src/oslat/oslat.c | 1 -
src/pi_tests/pi_stress.c | 1 -
src/pmqtest/pmqtest.c | 1 -
src/ptsematest/ptsematest.c | 1 -
src/rt-migrate-test/rt-migrate-test.c | 1 -
src/sched_deadline/cyclicdeadline.c | 1 -
src/signaltest/signaltest.c | 1 -
src/sigwaittest/sigwaittest.c | 1 -
src/ssdd/ssdd.c | 1 -
src/svsematest/svsematest.c | 1 -
14 files changed, 14 insertions(+), 30 deletions(-)
--
2.31.1
reply other threads:[~2021-06-30 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210630032330.17973-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=dwagner@suse.de \
--cc=efault@gmx.de \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®