linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: rt-users <linux-rt-users@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [ANNOUNCE] rt-tests-1.5
Date: Wed, 14 Aug 2019 17:49:29 +0200	[thread overview]
Message-ID: <20190814154929.9481-1-jkacur@redhat.com> (raw)

Mostly small clean-ups and bug fixes,

There was a fix to a bug where the paramater to -t was being ignored if 
the user didn't also specify the affinity -a.

This was a bit of fallout from the changes to automatically use numa if
support for it is available.

Bug reports and patches, are always welcome.

John Kacur

Clone
git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
branches

Branches
unstable/devel/latest (rt-tests: Version 1.5)
unstable/devel/latest-devel (for latest development of Version 1.5)

tarballs are available here
https://kernel.org/pub/linux/utils/rt-tests

older version tarballs are available to in
https://kernel.org/pub/linux/utils/rt-tests/older

John Kacur (3):
  rt-tests: Use gettid from rt-utils.c everywhere
  rt-tests: hwlatdetect: Remove kmodule options and clean-up help
  rt-tests: cyclictest: Without -t default to 1 thread in numa case

Kurt Kanzenbach (6):
  rt-tests: deadline: Remove duplicated code for sched_{set,get}_attr
  rt-tests: cyclicdeadline: Remove unused getcpu code
  rt-tests: deadline: Remove duplicated gettid() code
  rt-tests: cyclicdeadline: Add options to usage
  rt-tests: cyclicdeadline: Print fail only if something failed
  rt-tests: cyclicdeadline: Fix cgroup setup

Qiao Zhao (1):
  ptsematest, sigwaittest, pmqtest, svsematest reprot error "Could not
    access /sys/kernel/debug/tracing/tracing_enabled"

 src/cyclictest/cyclictest.c           | 13 ++---
 src/hwlatdetect/hwlatdetect.8         | 43 +++++++--------
 src/hwlatdetect/hwlatdetect.py        | 12 +----
 src/pmqtest/pmqtest.c                 |  4 +-
 src/ptsematest/ptsematest.c           |  4 +-
 src/rt-migrate-test/rt-migrate-test.c |  2 -
 src/sched_deadline/cyclicdeadline.c   | 71 ++++++------------------
 src/sched_deadline/deadline_test.c    | 78 ++-------------------------
 src/signaltest/signaltest.c           |  3 --
 src/sigwaittest/sigwaittest.c         |  4 +-
 src/svsematest/svsematest.c           |  4 +-
 11 files changed, 51 insertions(+), 187 deletions(-)

-- 
2.20.1


                 reply	other threads:[~2019-08-14 15:49 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=20190814154929.9481-1-jkacur@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).