mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: hansg@kernel.org, srinivas.pandruvada@linux.intel.com,
	ilpo.jarvinen@linux.intel.com
Cc: linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, dedekind1@gmail.com,
	artem.bityutskiy@linux.intel.com, m.wieczorretman@pm.me
Subject: [PATCH v1 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs
Date: Fri, 27 Mar 2026 15:36:30 +0000	[thread overview]
Message-ID: <cover.1774625521.git.m.wieczorretman@pm.me> (raw)

In TPMI devices, an instance is a feature copy that's local to the TPMI
device. It has its own control and header registers and it is tied to a
die that is a unit of uncore control.

Uncore Frequency Scaling (UFS) is a special feature in the sense that it
can have instances further split into clusters if there is more than one
per-die.

On older systems the domain_id value exported in sysfs matches the
instance value, as in it is unique in the single TPMI device scope. But
on newer systems that can have multiple clusters on a single die, the
intel-uncore-freq driver behaves differently and the domain_id is a
globally unique value - unique on all TPMI devices. Therefore it's
difficult to match a specific instance to a set of UFS registers for
example visible through /sys/kernel/debug/tpmi directories.

Separately exporting the instance value that's local to a TPMI device
and not globally unique can help restore the now lost value association.

Maciej Wieczor-Retman (2):
  platform/x86/intel-uncore-freq: Rename instance_id
  platform/x86/intel-uncore-freq: Expose instance ID in the sysfs

 .../uncore-frequency/uncore-frequency-common.c  | 16 +++++++++++++---
 .../uncore-frequency/uncore-frequency-common.h  |  8 ++++++--
 .../uncore-frequency/uncore-frequency-tpmi.c    | 17 ++++++++++++++++-
 3 files changed, 35 insertions(+), 6 deletions(-)

-- 
2.53.0



             reply	other threads:[~2026-03-27 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 15:36 Maciej Wieczor-Retman [this message]
2026-03-27 15:36 ` [PATCH v1 1/2] platform/x86/intel-uncore-freq: Rename instance_id Maciej Wieczor-Retman
2026-03-27 17:56   ` Artem Bityutskiy
2026-03-27 21:06     ` Maciej Wieczor-Retman
2026-03-27 15:36 ` [PATCH v1 2/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-03-27 17:51 ` [PATCH v1 0/2] " Artem Bityutskiy
2026-03-27 21:03   ` Maciej Wieczor-Retman
2026-03-29 19:30     ` srinivas pandruvada
2026-03-30  8:11       ` Maciej Wieczor-Retman
2026-03-30 17:10         ` srinivas pandruvada
2026-03-30 17:52           ` Maciej Wieczor-Retman

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=cover.1774625521.git.m.wieczorretman@pm.me \
    --to=m.wieczorretman@pm.me \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.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

all inboxes | Powered by JetHome®