From: Crystal Wood <crwood@redhat.com>
To: John Kacur <jkacur@redhat.com>, "John B. Wyatt IV" <jwyatt@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org,
kernel-rts-sst <kernel-rts-sst@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: Re: [PATCH 0/2] Add cpupower idle-state functionality
Date: Wed, 12 Feb 2025 14:53:35 -0600 [thread overview]
Message-ID: <50cda06eaa30769ebb2c3130fce5394f1d8bd9ad.camel@redhat.com> (raw)
In-Reply-To: <21714eaf-d3d8-81bd-cc27-7a8aeb0bf971@redhat.com>
On Mon, 2025-02-10 at 14:50 -0500, John Kacur wrote:
>
> On Mon, 27 Jan 2025, John B. Wyatt IV wrote:
>
> > This patch series adds idle-state functionality to control cpu power
> > usage and to test idle states.
> >
> > The number of cpus was needed in the cpupower file; I extracted out the
> > previously local to tuna-cli.py functionality to a separate file so the
> > cpu code can be used in any file in Tuna and reduce duplications. The
> > nics code was similar so it was also extracted to reduce the number of
> > global variables.
> >
> > Sincerely,
> > John Wyatt
> > Software Engineer, Core Kernel
> > Red Hat
> >
> > John B. Wyatt IV (2):
> > tuna: extract cpu and nics determination code into a utils.py file
> > tuna: Add idle-state control functionality
> >
> > tuna-cmd.py | 67 +++++++++-------
> > tuna/cpupower.py | 202 +++++++++++++++++++++++++++++++++++++++++++++++
> > tuna/utils.py | 27 +++++++
> > 3 files changed, 267 insertions(+), 29 deletions(-)
> > create mode 100755 tuna/cpupower.py
> > create mode 100644 tuna/utils.py
> >
> > --
> > 2.48.1
> >
> >
> >
> ./tuna-cmd.py idle-set -h
> usage: tuna-cmd.py idle-set [-h] [-c CPU-LIST]
> (-s IDLESTATEDISABLEDSTATUS | -i | -d
> IDLESTATEINDEX | -e IDLESTATEINDEX)
>
> Query and set all idle states on a given CPU list. Requires libcpupower to
> be
> installed
>
> options:
> -h, --help show this help message and exit
> -c CPU-LIST, --cpus CPU-LIST
> CPU-LIST affected by commands
> -s IDLESTATEDISABLEDSTATUS, --status IDLESTATEDISABLEDSTATUS
> Print if cpu idle state of the cpus in CPU-LIST is
> enabled or disabled. If CPU-LIST is not specified,
> default to all cpus.
> -i, --idle-info Print general idle information on cpus in
> CPU-LIST. If
> CPU-LIST is not specified, default to all cpus.
> -d IDLESTATEINDEX, --disable IDLESTATEINDEX
> Disable cpus in CPU-LIST's cpu idle (cpu sleep
> state).
> If CPU-LIST is not specified, default to all cpus.
> -e IDLESTATEINDEX, --enable IDLESTATEINDEX
> Enable cpus in CPU-LIST's cpu idle (cpu sleep
> state).
> If CPU-LIST is not specified, default to all cpus.
>
> These names are kind of awkward, isn't IDLESTATE good enough, why
> IDLESTATEINDEX?
>
> For the -s option, why do we need to put the IDLESTATEDISABLEDSTATUS, if
> we omit that can't we just get a result like running "cpupower idle-info"?
> Could you rename IDLESTATEDISABLEDSTATUS to just IDLESTATE_STATUS?
This was confusing to me too, but it looks like the argument is actually
a particular idle state, not the status of that state. So it should be
"IDLESTATE" just like -d and -e. Or better, "IDLE-STATE" like "CPU-
LIST".
-Crystal
next prev parent reply other threads:[~2025-02-12 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 1:45 [PATCH 0/2] Add cpupower idle-state functionality John B. Wyatt IV
2025-01-28 1:45 ` [PATCH 1/2] tuna: extract cpu and nics determination code into a utils.py file John B. Wyatt IV
2025-01-28 1:45 ` [PATCH 2/2] tuna: Add idle-state control functionality John B. Wyatt IV
2025-02-13 23:09 ` Crystal Wood
2025-02-19 18:23 ` John B. Wyatt IV
2025-02-10 19:50 ` [PATCH 0/2] Add cpupower idle-state functionality John Kacur
2025-02-12 20:53 ` Crystal Wood [this message]
2025-02-12 21:24 ` John B. Wyatt IV
2025-02-13 17:05 ` John Kacur
2025-02-13 18:45 ` Crystal Wood
2025-02-19 18:23 ` John B. Wyatt IV
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=50cda06eaa30769ebb2c3130fce5394f1d8bd9ad.camel@redhat.com \
--to=crwood@redhat.com \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=kernel-rts-sst@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=sageofredondo@gmail.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).