mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Erwan Velu <erwanaliasr1@gmail.com>, platform-driver-x86@vger.kernel.org
Cc: "Naveen Krishna Chatradhi" <naveenkrishna.chatradhi@amd.com>,
	"Carlos Bilbao" <carlos.bilbao@kernel.org>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] platform/x86/amd/hsmp: Add pwr_current_active_freq_limit_source_raw
Date: Sun, 1 Nov 2026 18:41:33 -0800	[thread overview]
Message-ID: <d9b0d35b-a8e8-4ffb-b2c4-a659ff7e941c@gmail.com> (raw)
In-Reply-To: <20261007125908.321186-5-erwanaliasr1@gmail.com>

On 10/7/26 05:59, Erwan Velu wrote:

> From: Erwan Velu <e.velu@criteo.com>
>
> pwr_current_active_freq_limit_source reports the active frequency limit
> sources as a list of names, one per line, which metrics exporters have
> to parse and map back to a value.
>
> Add pwr_current_active_freq_limit_source_raw, reporting the same source
> bitmask as a single hexadecimal value. Exporters only need a plain
> integer conversion, and its interpretation can be centralized in the
> monitoring stack, e.g. with Grafana value mappings, instead of being
> decoded on each server.
>
> The bit assignment is defined by the HSMP specification and is stable:
> new limit sources are only appended, existing bits never change meaning.
> A given value therefore has a single interpretation, whatever the
> platform or kernel version it comes from.
>
> Assisted-by: claude-opus-5-5
> Signed-off-by: Erwan Velu <e.velu@criteo.com>


Acked-by: Carlos Bilbao <carlos.bilbao@kernel.org>


> ---
>   Documentation/arch/x86/amd_hsmp.rst   |  4 ++++
>   drivers/platform/x86/amd/hsmp/sysfs.c | 18 ++++++++++++++++++
>   2 files changed, 22 insertions(+)
>
> diff --git a/Documentation/arch/x86/amd_hsmp.rst b/Documentation/arch/x86/amd_hsmp.rst
> index 954e938eea3d..66dbf506db05 100644
> --- a/Documentation/arch/x86/amd_hsmp.rst
> +++ b/Documentation/arch/x86/amd_hsmp.rst
> @@ -109,6 +109,10 @@ Following sysfs files are available at /sys/devices/amd_hsmp/socket%d/.
>     in MHz.
>   * pwr_current_active_freq_limit_source: Source of current active frequency
>     limit.
> +* pwr_current_active_freq_limit_source_raw: Source of current active
> +  frequency limit, as a hexadecimal bitmask. Bits 0 to 7 are, in order:
> +  cHTC-Active, PROCHOT, TDC limit, PPT Limit, OPN Max, Reliability Limit,
> +  APML Agent, HSMP Agent.
>   
>   ACPI device object format
>   =========================
> diff --git a/drivers/platform/x86/amd/hsmp/sysfs.c b/drivers/platform/x86/amd/hsmp/sysfs.c
> index e9e91b640b2a..fa1cf8dc3b6f 100644
> --- a/drivers/platform/x86/amd/hsmp/sysfs.c
> +++ b/drivers/platform/x86/amd/hsmp/sysfs.c
> @@ -274,6 +274,21 @@ static ssize_t hsmp_freq_limit_source_show(struct device *dev, struct device_att
>   	return len;
>   }
>   
> +static ssize_t hsmp_freq_limit_source_raw_show(struct device *dev,
> +					       struct device_attribute *attr, char *buf)
> +{
> +	struct hsmp_sys_attr *hattr = to_hsmp_sys_attr(attr);
> +	struct hsmp_socket *sock = dev_get_drvdata(dev);
> +	u32 data;
> +	int ret;
> +
> +	ret = hsmp_msg_get_nargs(sock->sock_ind, hattr->msg_id, &data, 1);
> +	if (ret)
> +		return ret;
> +
> +	return sysfs_emit(buf, "0x%04lx\n", FIELD_GET(FREQ_SRC_IND_MASK, data));
> +}
> +
>   static const struct bin_attribute  hsmp_metric_tbl_attr = {
>   	.attr = { .name = HSMP_METRICS_TABLE_NAME, .mode = 0444},
>   	.read = hsmp_metric_tbl_acpi_read,
> @@ -307,6 +322,8 @@ HSMP_DEV_ATTR(pwr_current_active_freq_limit, HSMP_GET_SOCKET_FREQ_LIMIT,
>   	      hsmp_freq_limit_show, 0444);
>   HSMP_DEV_ATTR(pwr_current_active_freq_limit_source, HSMP_GET_SOCKET_FREQ_LIMIT,
>   	      hsmp_freq_limit_source_show, 0444);
> +HSMP_DEV_ATTR(pwr_current_active_freq_limit_source_raw, HSMP_GET_SOCKET_FREQ_LIMIT,
> +	      hsmp_freq_limit_source_raw_show, 0444);
>   
>   static struct attribute *hsmp_dev_attr_list[] = {
>   	&hattr_c0_residency_input.dattr.attr,
> @@ -323,6 +340,7 @@ static struct attribute *hsmp_dev_attr_list[] = {
>   	&hattr_clk_fmin.dattr.attr,
>   	&hattr_pwr_current_active_freq_limit.dattr.attr,
>   	&hattr_pwr_current_active_freq_limit_source.dattr.attr,
> +	&hattr_pwr_current_active_freq_limit_source_raw.dattr.attr,
>   	NULL
>   };
>   

      reply	other threads:[~2026-11-02  2:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:59 [PATCH 0/4] platform/x86/amd/hsmp: Unify per-socket sysfs metrics Erwan Velu
2026-10-07 12:59 ` [PATCH 1/4] platform/x86/amd/hsmp: Move per-socket sysfs attributes to common code Erwan Velu
2026-11-02  2:38   ` Carlos Bilbao
2026-10-07 12:59 ` [PATCH 2/4] platform/x86/amd/hsmp: Add /sys/devices/amd_hsmp socket devices Erwan Velu
2026-10-16 11:02   ` Ilpo Järvinen
2026-11-02  2:57   ` Carlos Bilbao
2026-10-07 12:59 ` [PATCH 3/4] platform/x86/amd/hsmp: Expose socket attributes from the platform driver Erwan Velu
2026-10-07 12:59 ` [PATCH 4/4] platform/x86/amd/hsmp: Add pwr_current_active_freq_limit_source_raw Erwan Velu
2026-11-02  2:41   ` Carlos Bilbao [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=d9b0d35b-a8e8-4ffb-b2c4-a659ff7e941c@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=erwanaliasr1@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenkrishna.chatradhi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®