From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Avadhut Naik <avadnaik@amd.com>,
"Wilczynski, Michal" <michal.wilczynski@intel.com>,
Avadhut Naik <avadhut.naik@amd.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] ACPI: PHAT: Add Platform Health Assessment Table support
Date: Mon, 21 Aug 2023 14:23:07 -0500 [thread overview]
Message-ID: <0c1fcac6-5497-4a0d-9038-9eebf988268e@amd.com> (raw)
In-Reply-To: <CAJZ5v0i-=kfBPp2oW-40mNSAFnOzTEeey0EhDUsN6qNU+QY4Ug@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-08-21 19:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:48 [PATCH] ACPI: PHAT: Add Platform Health Assessment Table support Avadhut Naik
2023-08-11 22:52 ` Avadhut Naik
2023-08-16 11:35 ` Wilczynski, Michal
2023-08-17 20:42 ` Avadhut Naik
2023-08-18 7:49 ` Rafael J. Wysocki
2023-08-21 17:06 ` Limonciello, Mario
2023-08-21 17:12 ` Rafael J. Wysocki
2023-08-21 17:17 ` Limonciello, Mario
2023-08-21 17:29 ` Rafael J. Wysocki
2023-08-21 17:35 ` Limonciello, Mario
2023-08-21 17:52 ` Rafael J. Wysocki
2023-08-21 18:00 ` Limonciello, Mario
2023-08-21 18:04 ` Rafael J. Wysocki
2023-08-21 18:01 ` Rafael J. Wysocki
2023-08-21 18:44 ` Yazen Ghannam
2023-08-21 18:49 ` Rafael J. Wysocki
2023-08-21 19:01 ` Yazen Ghannam
2023-08-21 19:16 ` Rafael J. Wysocki
2023-08-21 19:23 ` Limonciello, Mario [this message]
2023-08-21 23:33 ` Yazen Ghannam
2023-08-22 2:53 ` Limonciello, Mario
2023-08-22 2:26 ` Avadhut Naik
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=0c1fcac6-5497-4a0d-9038-9eebf988268e@amd.com \
--to=mario.limonciello@amd.com \
--cc=avadhut.naik@amd.com \
--cc=avadnaik@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.wilczynski@intel.com \
--cc=rafael@kernel.org \
--cc=yazen.ghannam@amd.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