From: Tomas Glozar <tglozar@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Tomas Glozar <tglozar@redhat.com>
Subject: [PATCH 0/6] rteval: Handle isolcpus correctly
Date: Fri, 30 Jun 2023 11:19:01 +0200 [thread overview]
Message-ID: <20230630091951.916865-1-tglozar@redhat.com> (raw)
This is a patch set that enables rteval to do load calculations and reporting
correctly on systems with isolated CPUs.
Tomas Glozar (6):
rteval: Detect isolcpus in systopology
rteval: Report isolated CPUs
rteval: Exclude isolcpus from kcompile by default
rteval: Exclude isolcpus from stressng by default
rteval: Fix CPU count calculation for hackbench
rteval: Exclude isolcpus from loads report
rteval/modules/loads/__init__.py | 2 +-
rteval/modules/loads/hackbench.py | 6 +++-
rteval/modules/loads/kcompile.py | 8 +++--
rteval/modules/loads/stressng.py | 5 +++
rteval/modules/measurement/__init__.py | 2 +-
rteval/rteval_text.xsl | 4 +++
rteval/sysinfo/cputopology.py | 11 +++++++
rteval/systopology.py | 43 ++++++++++++++++++++++++++
8 files changed, 76 insertions(+), 5 deletions(-)
--
2.41.0
next reply other threads:[~2023-06-30 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 9:19 Tomas Glozar [this message]
2023-06-30 9:19 ` [PATCH 1/6] rteval: Detect isolcpus in systopology Tomas Glozar
2023-07-25 13:33 ` John Kacur
2023-07-25 13:36 ` John Kacur
2023-06-30 9:19 ` [PATCH 2/6] rteval: Report isolated CPUs Tomas Glozar
2023-07-25 13:38 ` John Kacur
2023-06-30 9:19 ` [PATCH 3/6] rteval: Exclude isolcpus from kcompile by default Tomas Glozar
2023-07-25 13:40 ` John Kacur
2023-06-30 9:19 ` [PATCH 4/6] rteval: Exclude isolcpus from stressng " Tomas Glozar
2023-07-25 13:42 ` John Kacur
2023-06-30 9:19 ` [PATCH 5/6] rteval: Fix CPU count calculation for hackbench Tomas Glozar
2023-07-25 13:44 ` John Kacur
2023-06-30 9:19 ` [PATCH 6/6] rteval: Exclude isolcpus from loads report Tomas Glozar
2023-07-25 14:32 ` 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=20230630091951.916865-1-tglozar@redhat.com \
--to=tglozar@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 NNTP newsgroup(s).