From: John Kacur <jkacur@redhat.com>
To: Linux RT Users <linux-rt-users@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Clark Williams <williams@redhat.com>
Subject: [ANNOUNCE] New release rt-tests-1.4
Date: Thu, 20 Jun 2019 15:26:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.21.1906201444220.6702@planxty> (raw)
We haven't had a release in a while as people were content to work from
git. However, in order to make it easier to use, test, and put into
distributions, now would be a good time for an official release.
There have been a number of interesting changes since 1.3
I'm happy with the way the removal of the --numa from cyclictest is
working now. What this means is that numa is dectected automatically, so
you don't have to specify it. You can still force smp with --smp though.
In addition, cpu affinity should work correctly now. Historically there
were combinations of options in which you couldn't specify cpu affinity,
but these restrictions have been removed.
We have added a number of new programs to the rt-tests suite
- queuelat
- cyclicdeadline
- deadline_test
- ssdd
queuelat simulates a network queue checking for latency violations in
packet processing.
deadline_test is used to test the deadline scheduler (SCHED_DEADLINE)
cyclicdeadline also tests the deadline scheduler in a cyclictest manner
ssdd has a tracer do a bunch of PTRACE_SINGLESTEPs
There is a new feature that adds a duration option to many of the tests
as a more natural way that iterations to determine how long to test for.
There have also been a number of fix and updates, such as an update.
hwlatdetect no-longer requires a kernel module, instead it uses ftrace.
It also works with python3
CPU counters with SMI counter support has been updated, although I think
we're due for another. Hint to Daniel :)
So the latest stable / unstable branch (yes the naming is confusing, and
this will be changed in the future too) is
unstable/devel/latest
If you just to want to use or test the latest then use that
Development for the above is happening here
unstable/devel/latest-devel
This already has some new patches for the deadline tests
This is what developers should development against until
I merge it back into the latest.
Bug reports and patches, are all welcome.
I'd like to step up development, especially bug fixes, and
harden this up. Everything is working reasonably well, but
I'm sure with everyone working the code we can flush out some bugs
and aim for a new stable branch.
So, have fun, and send in your patches and reports!
John Kacur
Clone
git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
branches
Branches
unstable/devel/latest (rt-tests: Version 1.4)
unstable/devel/latest-devel (for latest development of Version 1.4)
tarballs are available here
https://kernel.org/pub/linux/utils/rt-tests/
next reply other threads:[~2019-06-20 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:26 John Kacur [this message]
2019-06-21 6:58 ` [ANNOUNCE] New release rt-tests-1.4 David Runge
2019-06-21 12:08 ` John Kacur
2019-06-24 14:36 ` David Runge
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=alpine.LFD.2.21.1906201444220.6702@planxty \
--to=jkacur@redhat.com \
--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