From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "John B. Wyatt IV" <jwyatt@redhat.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-pm@vger.kernel.org, Thomas Renninger <trenn@suse.com>,
Shuah Khan <shuah@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, John Kacur <jkacur@redhat.com>,
Tomas Glozar <tglozar@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: Re: [PATCH 0/2][RFC] Add SWIG Bindings to libcpupower
Date: Sun, 4 Aug 2024 10:54:10 +0200 [thread overview]
Message-ID: <2024080405-roundish-casket-2474@gregkh> (raw)
In-Reply-To: <Zqv9BOjxLAgyNP5B@hatbackup>
On Thu, Aug 01, 2024 at 05:24:20PM -0400, John B. Wyatt IV wrote:
> > On 7/24/24 16:11, John B. Wyatt IV wrote:
> > > SWIG is a tool packaged in Fedora and other distros that can generate
> > > bindings from C and C++ code for several languages including Python,
> > > Perl, and Go. We at Red Hat are interested in adding binding support to
> > > libcpupower so Python tools like rteval or tuned can make easy use of it.
> > >
> >
> > Can you elaborate on the use-case and what rteval currently does and
> > how it could benefit from using libcpupower with the bindings?
>
> rteval is a Python program used to measure realtime performance. We wanted to
> test the effect of enabling some levels of idle-stat to see how it affects
> latency, and didn't want to reinvent the wheel. We thought that the Python
> bindings could be useful to other people as well who might want to call
> cpupower too from Python. I did some testing and was able to achieve this with
> SWIG. We sent the patchset to see what folks thought about this.
Is this going to require a built-time dependency on SWIG? If not, when
would it be run, and who will be in charge of running it and updating
the bindings?
And finally, why do we need these at all? You are saying these are new
tests that external tools will be using, but why, if external tools are
required to run them, are they needed in the kernel tree at all? Why
isn't this just another external test-suite that people who care about
measuring this type of thing going to just run on their own if desired?
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-04 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 22:11 [PATCH 0/2][RFC] Add SWIG Bindings to libcpupower John B. Wyatt IV
2024-07-24 22:11 ` [PATCH 1/2] Add SWIG bindings files for libcpupower John B. Wyatt IV
2024-07-24 22:11 ` [PATCH 2/2] Include test_raw_pylibcpupower.py John B. Wyatt IV
2024-07-26 17:34 ` [PATCH 0/2][RFC] Add SWIG Bindings to libcpupower Shuah Khan
2024-07-30 20:48 ` Shuah Khan
2024-08-01 21:24 ` John B. Wyatt IV
2024-08-04 8:54 ` Greg Kroah-Hartman [this message]
2024-08-06 20:56 ` John B. Wyatt IV
2024-08-20 6:40 ` John B. Wyatt IV
2024-08-21 7:08 ` Shuah Khan
2024-08-22 3:25 ` Shuah Khan
2024-08-27 17:58 ` John B. Wyatt IV
2024-08-09 20:25 ` Arnaldo Carvalho de Melo
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=2024080405-roundish-casket-2474@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sageofredondo@gmail.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglozar@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.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).