From: "Teddy Astie" <teddy.astie@vates.tech>
To: xen-devel@lists.xenproject.org
Cc: "Teddy Astie" <teddy.astie@vates.tech>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: [RFC PATCH for-4.22 v2 0/3] Support for Intel temperature sensors (DTS)
Date: Wed, 29 Oct 2025 15:59:33 +0000 [thread overview]
Message-ID: <cover.1761752801.git.teddy.astie@vates.tech> (raw)
The idea here is to expose the DTS sensors through XENPF_resource_op
and expose it for the user through xenpm.
v2:
- moved userland part to xenpm
- use cpu policy infrastructure instead of inline cpuid
Teddy Astie (3):
x86/cpu-policy: Infrastructure for CPUID leaf 0x6
x86/platform: Expose DTS sensors MSR
xenpm: Add get-intel-temp subcommand
tools/misc/xenpm.c | 93 +++++++++++++++++++++++++++-
xen/arch/x86/include/asm/msr-index.h | 3 +
xen/arch/x86/platform_hypercall.c | 6 ++
xen/include/xen/lib/x86/cpu-policy.h | 27 +++++++-
4 files changed, 127 insertions(+), 2 deletions(-)
--
2.51.2
--
Teddy Astie | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next reply other threads:[~2025-10-29 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 15:59 Teddy Astie [this message]
2025-10-29 15:59 ` [RFC PATCH for-4.22 v2 3/3] xenpm: Add get-intel-temp subcommand Teddy Astie
2025-10-30 14:02 ` Jan Beulich
2025-11-03 14:34 ` Teddy Astie
2025-10-29 15:59 ` [RFC PATCH for-4.22 v2 1/3] x86/cpu-policy: Infrastructure for CPUID leaf 0x6 Teddy Astie
2025-10-30 7:12 ` Jan Beulich
2025-10-30 10:10 ` Teddy Astie
2025-10-29 15:59 ` [RFC PATCH for-4.22 v2 2/3] x86/platform: Expose DTS sensors MSR Teddy Astie
2025-10-30 13:54 ` Jan Beulich
2025-11-03 14:30 ` Teddy Astie
2025-11-06 8:14 ` Jan Beulich
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.1761752801.git.teddy.astie@vates.tech \
--to=teddy.astie@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.