From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Crystal Wood <crwood@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: John Kacur <jkacur@redhat.com>,
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 16:24:14 -0500 [thread overview]
Message-ID: <Z60Rfi05LXbjGfHi@thinkpad2024> (raw)
In-Reply-To: <50cda06eaa30769ebb2c3130fce5394f1d8bd9ad.camel@redhat.com>
On Wed, Feb 12, 2025 at 02:53:35PM -0600, Crystal Wood wrote:
> On Mon, 2025-02-10 at 14:50 -0500, John Kacur wrote:
> > 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
>
Apologies for not answering you earlier John. Did not see this email until
Crystal's email.
If there is no objections I will go with Crystal's suggestion.
Here is the current printout for the patch series I will send (note I changed
a few items to address confusion). Please let me know if this addresses
everyone's concerns:
options:
-h, --help show this help message and exit
-i, --idle-info Print general idle information on cpus in CPU-LIST. If CPU-LIST is not specified, default to all cpus.
-s IDLE-STATE, --status IDLE-STATE
Print the idle-state (cpu sleep state) of the cpus in CPU-LIST as enabled or disabled. The argument is the index of the idle-state of the cpu as reported by -i. If
CPU-LIST is not specified, default to all cpus.
-d IDLE-STATE, --disable IDLE-STATE
Disable cpus in CPU-LIST's idle-state (cpu sleep state). The argument is the index of the idle-state of the cpu as reported by -i. If CPU-LIST is not specified,
default to all cpus.
-e IDLE-STATE, --enable IDLE-STATE
Enable cpus in CPU-LIST's idle-state (cpu sleep state). The argument is the index of the idle-state of the cpu as reported by -i. If CPU-LIST is not specified,
default to all cpus.
-c CPU-LIST, --cpus CPU-LIST
CPU-LIST affected by commands
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
next prev parent reply other threads:[~2025-02-12 21:24 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
2025-02-12 21:24 ` John B. Wyatt IV [this message]
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=Z60Rfi05LXbjGfHi@thinkpad2024 \
--to=jwyatt@redhat.com \
--cc=crwood@redhat.com \
--cc=jkacur@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).