On 8/21/2023 2:16 PM, Rafael J. Wysocki wrote:
<snip>
Is there a preferred set of tools that can be updated?
I think you need to talk to distro people about this.
If not, would it make sense to develop a set of common kernel tools for
this?
Yes, it would, but please see above in the first place.
In my experience, it seems many folks use tools from their vendors or
custom tools.
This observation matches my own experience.
For the sake of discussion, and from a kernel developer's point of view,
should the tools be part of a separate project? Or should the tools be
part of the kernel tree like perf, etc.? Assuming that this needs to
start from scratch and not extending an existing project.
It can be both in principle, but from the practical standpoint it is
more likely to get all of the people to use the same set of tools if
they are included into the kernel source tree.
Yazen,
You generally envision tools like this to only be used when there is a
problem, and not something that's run critical path on every boot right?
If so, how about doing it in a high level language with easily
importable libraries like Python?
Then the tools can still be stored "in kernel tree" and distributed with
distro "kernel tools" packages but you can more easily use them on
random old kernels too since the binary via /sys/firmware/acpi/tables
should be widely available.
