From: Crystal Wood <crwood@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org
Subject: [PATCH 0/4] rt-tests: cyclicdeadline: Add histogram support
Date: Wed, 6 Dec 2023 14:55:04 -0600 [thread overview]
Message-ID: <20231206205508.17148-1-crwood@redhat.com> (raw)
Add histogram support to cyclicdeadline, with the goal of supporting
cyclicdeadline in rteval. New output-compatible (except for the change
in patch 2/4) histogram code is used, to ease sharing. The new code is
intended to also be usable by other measurers such as oslat.
Crystal Wood (4):
rt-tests: Fix warnings
rt-tests: cyclictest: Remove histogram totals
rt-tests: cyclictest: Replace histogram code with library
rt-tests: cyclicdeadline: Add histogram support
Makefile | 5 +-
src/cyclictest/cyclictest.c | 94 ++++-----------
src/hackbench/hackbench.c | 2 +-
src/include/histogram.h | 42 +++++++
src/lib/histogram.c | 174 ++++++++++++++++++++++++++++
src/sched_deadline/cyclicdeadline.c | 119 ++++++++++++++++---
src/sched_deadline/deadline_test.c | 10 +-
src/sigwaittest/sigwaittest.c | 6 +-
8 files changed, 357 insertions(+), 95 deletions(-)
create mode 100644 src/include/histogram.h
create mode 100644 src/lib/histogram.c
--
2.43.0
next reply other threads:[~2023-12-06 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 20:55 Crystal Wood [this message]
2023-12-06 20:55 ` [PATCH 1/4] rt-tests: Fix warnings Crystal Wood
2023-12-13 15:41 ` John Kacur
2023-12-14 15:48 ` John Kacur
2023-12-14 16:55 ` John Kacur
2023-12-18 20:15 ` Crystal Wood
2023-12-18 21:11 ` John Kacur
2023-12-06 20:55 ` [PATCH 2/4] rt-tests: cyclictest: Remove histogram totals Crystal Wood
2023-12-13 15:58 ` John Kacur
2023-12-13 16:18 ` Crystal Wood
2023-12-13 16:21 ` John Kacur
2023-12-06 20:55 ` [PATCH 3/4] rt-tests: cyclictest: Replace histogram code with library Crystal Wood
2023-12-06 20:55 ` [PATCH 4/4] rt-tests: cyclicdeadline: Add histogram support Crystal Wood
2023-12-14 16:10 ` 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=20231206205508.17148-1-crwood@redhat.com \
--to=crwood@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).