From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Crystal Wood <crwood@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, 19 Feb 2025 13:23:56 -0500 [thread overview]
Message-ID: <Z7YhvMPx8FZ03IGv@thinkpad2024> (raw)
In-Reply-To: <2c97696aec2256cc15f2c045bfb313f7a7691c7c.camel@redhat.com>
On Thu, Feb 13, 2025 at 12:45:07PM -0600, Crystal Wood wrote:
>
> We could simplify the description as:
>
> -i, --idle-info Print general idle information for the selected CPUs,
> including index values for IDLE-STATE.
> -s IDLE-STATE, --status IDLE-STATE
> Print whether IDLE-STATE is enabled on the selected
> CPUs.
> -d IDLE-STATE, --disable IDLE-STATE
> Disable IDLE-STATE on the selected CPUs
> -e IDLE-STATE, --enable IDLE-STATE
> Enable IDLE-STATE on the selected CPUs
> -c CPU-LIST, --cpus CPU-LIST
> Specify the list of CPUs to act on. If omitted,
> act on all CPUs.
Will do. Thank you Crystal.
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
prev parent reply other threads:[~2025-02-19 18: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
2025-02-13 17:05 ` John Kacur
2025-02-13 18:45 ` Crystal Wood
2025-02-19 18:23 ` John B. Wyatt IV [this message]
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=Z7YhvMPx8FZ03IGv@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).