From: Artem Bityutskiy <dedekind1@gmail.com>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
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
Subject: Re: [PATCH v1 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs
Date: Fri, 27 Mar 2026 19:51:54 +0200 [thread overview]
Message-ID: <4a19dd6c2ee07bf70ac136747e1ea5bfd8e41888.camel@gmail.com> (raw)
In-Reply-To: <cover.1774625521.git.m.wieczorretman@pm.me>
On Fri, 2026-03-27 at 15:36 +0000, Maciej Wieczor-Retman wrote:
> 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.
Although, I'd say that the key point isn't that "domain_id is globally
unique" (though this is true), but that it's a synthetic value
generated by the driver rather than representing an actual HW instance
ID.
Artem.
next prev parent reply other threads:[~2026-03-27 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:36 Maciej Wieczor-Retman
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 ` Artem Bityutskiy [this message]
2026-03-27 21:03 ` [PATCH v1 0/2] " 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=4a19dd6c2ee07bf70ac136747e1ea5bfd8e41888.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--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
Powered by JetHome