From: Hans de Goede <hansg@kernel.org>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, mario.limonciello@amd.com,
Yijun.Shen@Dell.com, Sanket.Goswami@amd.com
Subject: Re: [PATCH v2 0/5] Introduce AMD PMF util layer and user-space interface for SystemDeck
Date: Wed, 19 Nov 2025 17:20:43 +0100 [thread overview]
Message-ID: <2c40e722-ffd7-4e00-92dd-2c89ff4768a0@kernel.org> (raw)
In-Reply-To: <20251111071010.4179492-1-Shyam-sundar.S-k@amd.com>
Hi Shyam,
On 11-Nov-25 8:10 AM, Shyam Sundar S K wrote:
> This series introduces a util layer to the AMD Platform Management
> Framework (PMF) and a minimal user-space interface via a misc character
> device, enabling feature discovery and smoother integration with
> user-space tools. It also adds caching of BIOS output policy values to
> prepare for user-space telemetry reporting via IOCTLs.
>
> The motivation is to provide a stable interface for user-space tools to
> discover PMF features and consume selected metrics. Enable smoother
> integration with AMD SystemDeck
This does not really explain why you've chosen for a new character-device
with IOCTLs instead of sysfs where as so far (AFAICT) all the AMD PMF code
has been using sysfs APIs.
Is there any specific reason why to switch to IOCTLs all of a sudden?
Note that:
1. sysfs APIs can be (and must be) stable too, sysfs APIs are not allowed
to be changed once shipped in a stable kernel.
2. sysfs attributes can be used with poll() to so if you want to do
notifications of changes that can be done through sysfs too.
Note I'm not saying you must use sysfs, but so far the PMF code has been
using sysfs everywhere and this new IOCTL based API is not really consistent
with this.
So at a minimum you are going to need some pretty good arguments to
deviate from just doing this with sysfs as has been done before.
Regards,
Hans
> , a widely used tool for monitoring and
> controlling power and thermal behavior, helping designers keep components
> within thermal limits to ensure proper operation and improve system
> stability and reliability.
>
> This series also adds a small, dependable userspace utility that leverages
> the new IOCTLs to query live power and thermal telemetry. Exposing this
> data in a scriptable interface helps users and tooling make informed,
> workload-aware decisions and supports validation and debugging.
>
> v2:
> ----
> - address remarks from v1
> - add a new tool that exercises the IOCTLs from PMF interface
>
> Shyam Sundar S K (5):
> platform/x86/amd/pmf: add util layer and user-space misc device
> interface
> platform/x86/amd/pmf: cache BIOS output values for user-space
> telemetry via util IOCTL
> Documentation/ABI: add testing entry for AMD PMF misc device interface
> platform/x86/amd/pmf: Store commonly used enums in the header file
> platform/x86/amd/pmf: Introduce AMD PMF testing tool for driver
> metrics and features
>
> .../ABI/testing/misc-amdpmf_interface | 49 +++
> MAINTAINERS | 1 +
> drivers/platform/x86/amd/pmf/Kconfig | 10 +
> drivers/platform/x86/amd/pmf/Makefile | 2 +
> drivers/platform/x86/amd/pmf/core.c | 19 +
> drivers/platform/x86/amd/pmf/pmf.h | 33 +-
> drivers/platform/x86/amd/pmf/spc.c | 1 +
> drivers/platform/x86/amd/pmf/tee-if.c | 10 +
> drivers/platform/x86/amd/pmf/util.c | 236 +++++++++++
> include/uapi/linux/amd-pmf.h | 96 +++++
> tools/testing/selftests/Makefile | 1 +
> .../drivers/platform/x86/amd/pmf/Makefile | 8 +
> .../drivers/platform/x86/amd/pmf/test_pmf.c | 388 ++++++++++++++++++
> 13 files changed, 832 insertions(+), 22 deletions(-)
> create mode 100644 Documentation/ABI/testing/misc-amdpmf_interface
> create mode 100644 drivers/platform/x86/amd/pmf/util.c
> create mode 100644 include/uapi/linux/amd-pmf.h
> create mode 100644 tools/testing/selftests/drivers/platform/x86/amd/pmf/Makefile
> create mode 100644 tools/testing/selftests/drivers/platform/x86/amd/pmf/test_pmf.c
>
next prev parent reply other threads:[~2025-11-19 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 7:10 [PATCH v2 0/5] Introduce AMD PMF util layer and user-space interface for SystemDeck Shyam Sundar S K
2025-11-11 7:10 ` [PATCH v2 1/5] platform/x86/amd/pmf: add util layer and user-space misc device interface Shyam Sundar S K
2025-11-11 7:10 ` [PATCH v2 2/5] platform/x86/amd/pmf: cache BIOS output values for user-space telemetry via util IOCTL Shyam Sundar S K
2025-11-18 16:18 ` Ilpo Järvinen
2025-11-26 9:36 ` Shyam Sundar S K
2025-11-11 7:10 ` [PATCH v2 3/5] Documentation/ABI: add testing entry for AMD PMF misc device interface Shyam Sundar S K
2025-11-11 7:10 ` [PATCH v2 4/5] platform/x86/amd/pmf: Store commonly used enums in the header file Shyam Sundar S K
2025-11-11 7:10 ` [PATCH v2 5/5] platform/x86/amd/pmf: Introduce AMD PMF testing tool for driver metrics and features Shyam Sundar S K
2025-11-12 18:07 ` Mario Limonciello
2025-11-12 18:08 ` [PATCH v2 0/5] Introduce AMD PMF util layer and user-space interface for SystemDeck Mario Limonciello
2025-11-13 7:30 ` Shyam Sundar S K
2025-11-19 16:20 ` Hans de Goede [this message]
2025-11-19 16:32 ` Mario Limonciello
2025-11-19 19:25 ` Hans de Goede
2025-11-20 7:49 ` Shyam Sundar S K
2025-11-24 10:04 ` Hans de Goede
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=2c40e722-ffd7-4e00-92dd-2c89ff4768a0@kernel.org \
--to=hansg@kernel.org \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=Yijun.Shen@Dell.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.