Linux Power Management development
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Lars Schellhas van Kisfeld
	<lars.schellhas-van-kisfeld@schellhasconsulting.de>,
	 "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [RFC] intel_rapl: exposing PL3 / PsysPL3 (MSR 0x615) through powercap?
Date: Tue, 17 Nov 2026 07:59:05 -0800	[thread overview]
Message-ID: <3435bb0b801bd63f989b04073b747c90c1ce4af5.camel@linux.intel.com> (raw)
In-Reply-To: <BEZSPRMB000259539D5BE9BD203C5455E87B2@BEZSPRMB0002.DEUP281.PROD.OUTLOOK.COM>

Hi Lars,
On Tue, 2026-11-17 at 10:27 +0000, Lars Schellhas van Kisfeld wrote:
> Hi,
> before writing a patch I'd like to ask whether this would be welcome.
> 
> Background: I'm working on a user-space daemon that applies the
> Windows
> power configuration of Microsoft Surface devices on Linux [1]. On
> Windows,
> Intel DTT writes MSR 0x615 dynamically as a platform peak limit. On a
> Surface Book 3 (Ice Lake) the firmware sets it to 65 W (enabled);
> Windows
> raises it to 100 W on AC. powercap has no constraint for it, so the
> daemon
> writes 0x615 through /dev/cpu//msr, which needs CAP_SYS_RAWIO, fails
> under
> lockdown and triggers the "unrecognized MSR" warning.
> 
> What I measured: on the SB3, 0x615 binds on platform (psys) power,
> not on
> package power. With 20 W in bits 14:0 and the enable bit as found,
> psys
> power under all-core load drops from ~35 W to ~18 W. Restoring the
> original
> value works. A tester saw the same write, bind and restore on an
> Alder Lake
> Surface Pro 9. coreboot also treats 0x615 as PsysPL3, next to 0x65C.
> 
> Questions:
> 1. Is 0x615 PsysPL3 (platform domain) on all client parts that have
> it, and
>     is its layout documented publicly (time window, duty cycle in
> bits
>     30:24, lock bit 31)? I couldn't find 615H in the public SDM.

This is not documented in SDM. So, will be difficult to add to Linux
kernel. When not documented, it is difficult to what each fields mean
and can change gen to gen.

Thanks,
Srinivas


> 2. Would you accept a third constraint on the psys domain for it,
> opt-in
>     per CPU model like msr_pl4_support? Duty cycle would stay
> untouched.
> 3. Any preference for the constraint name? "peak_power" is taken by
> PL4.
> 
> If this sounds reasonable, I'd send a patch for the models I can
> verify,
> and only those.
> Thanks,
> Lars
> 
> [1] https://github.com/larsschellhas/linux-surface-power

      reply	other threads:[~2026-11-17 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 10:27 [RFC] intel_rapl: exposing PL3 / PsysPL3 (MSR 0x615) through powercap? Lars Schellhas van Kisfeld
2026-11-17 15:59 ` srinivas pandruvada [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=3435bb0b801bd63f989b04073b747c90c1ce4af5.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=lars.schellhas-van-kisfeld@schellhasconsulting.de \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@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