From: John Kacur <jkacur@redhat.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>,
Tomas Glozar <tglozar@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH 00/12] rteval updates
Date: Fri, 7 Nov 2025 13:26:23 -0500 [thread overview]
Message-ID: <20251107182645.19545-1-jkacur@redhat.com> (raw)
Notable here are the patches to add
--measurement-module MODULE so that you can choose cyclictest or
timerlat without modifying the rteval.conf file
The patches that adds
--timerlat-dma_latency USEC
Set /dev/cpu_dma_latency to USEC (set to None to
disable) (default: 0)
And finally the addition of pyproject.toml for a modern type of python
install. We will still carry setup.py for older distributions.
John
John Kacur (12):
rteval: Fix spelling of 'occurrences' in measurement modules
rteval: Fix typo in comment
rteval: Remove unused function remove_offline
rteval: timerlat: Fix typo in log message
rteval: cyclictest: Fix typo in comment
rteval: rtevalConfig: Remove redundant 'is True' comparison
rteval: Clean up MANIFEST.in and fix newnet.py copyright header
rteval: Add pyproject.toml for modern Python packaging
rteval: Improve argparse implementation and remove manual sys.argv
parsing
rteval: timerlat: Add dma_latency option with default value of 0
rteval: Add --measurement-module command-line argument
rteval: Add unit tests for --measurement-module argument
MANIFEST.in | 3 +-
Makefile | 10 ++
pyproject.toml | 58 ++++++
rteval-cmd | 122 +++++++------
rteval/modules/__init__.py | 7 +
rteval/modules/measurement/__init__.py | 2 +-
rteval/modules/measurement/cyclictest.py | 8 +-
rteval/modules/measurement/timerlat.py | 17 +-
rteval/rtevalConfig.py | 2 +-
rteval/sysinfo/newnet.py | 3 +-
run_tests.sh | 89 ++++++++++
setup.py | 6 +-
tests/test_measurement_module_selection.py | 195 +++++++++++++++++++++
13 files changed, 443 insertions(+), 79 deletions(-)
create mode 100644 pyproject.toml
create mode 100755 run_tests.sh
create mode 100755 tests/test_measurement_module_selection.py
--
2.51.1
next reply other threads:[~2025-11-07 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 18:26 John Kacur [this message]
2025-11-07 18:26 ` [PATCH 01/12] rteval: Fix spelling of 'occurrences' in measurement modules John Kacur
2025-11-07 18:26 ` [PATCH 02/12] rteval: Fix typo in comment John Kacur
2025-11-07 18:26 ` [PATCH 03/12] rteval: Remove unused function remove_offline John Kacur
2025-11-07 18:26 ` [PATCH 04/12] rteval: timerlat: Fix typo in log message John Kacur
2025-11-07 18:26 ` [PATCH 05/12] rteval: cyclictest: Fix typo in comment John Kacur
2025-11-07 18:26 ` [PATCH 06/12] rteval: rtevalConfig: Remove redundant 'is True' comparison John Kacur
2025-11-07 18:26 ` [PATCH 07/12] rteval: Clean up MANIFEST.in and fix newnet.py copyright header John Kacur
2025-11-07 18:26 ` [PATCH 08/12] rteval: Add pyproject.toml for modern Python packaging John Kacur
2025-11-07 18:26 ` [PATCH 09/12] rteval: Improve argparse implementation and remove manual sys.argv parsing John Kacur
2025-11-07 18:26 ` [PATCH 10/12] rteval: timerlat: Add dma_latency option with default value of 0 John Kacur
2025-11-07 18:26 ` [PATCH 11/12] rteval: Add --measurement-module command-line argument John Kacur
2025-11-07 18:26 ` [PATCH 12/12] rteval: Add unit tests for --measurement-module argument 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=20251107182645.19545-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglozar@redhat.com \
--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).