public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	sk.anirban@intel.com, kamil.konieczny@intel.com
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] powercap: intel_rapl: Prepare read_raw interface for atomic-context callers
Date: Sat, 14 Feb 2026 07:37:17 +0100	[thread overview]
Message-ID: <aZAYHb0kO8eS0Z_5@black.igk.intel.com> (raw)
In-Reply-To: <20251121000539.386069-2-sathyanarayanan.kuppuswamy@linux.intel.com>

On Thu, Nov 20, 2025 at 04:05:38PM -0800, Kuppuswamy Sathyanarayanan wrote:
> The current read_raw() implementation of the TPMI, MMIO and MSR
> interfaces does not distinguish between atomic and non-atomic callers.
> 
> rapl_msr_read_raw() uses rdmsrq_safe_on_cpu(), which can sleep and
> issue cross CPU calls. When MSR-based RAPL PMU support is enabled, PMU
> event handlers can invoke this function from atomic context where
> sleeping or rescheduling is not allowed. In atomic context, the caller
> is already executing on the target CPU, so a direct rdmsrq() is
> sufficient.
> 
> To support such usage, introduce an atomic flag to the read_raw()
> interface to allow callers pass the context information. Modify the
> common RAPL code to propagate this flag, and set the flag to reflect
> the calling contexts.
> 
> Utilize the atomic flag in rapl_msr_read_raw() to perform direct MSR
> read with rdmsrq() when running in atomic context, and a sanity check
> to ensure target CPU matches the current CPU for such use cases.
> 
> The TPMI and MMIO implementations do not require special atomic
> handling, so the flag is ignored in those paths.
> 
> This is a preparatory patch for adding MSR-based RAPL PMU support.

...

> -static int rapl_msr_read_raw(int cpu, struct reg_action *ra)
> +static int rapl_msr_read_raw(int cpu, struct reg_action *ra, bool atomic)
>  {
> +	/*
> +	 * When called from atomic-context (eg PMU event handler)
> +	 * perform MSR read directly using rdmsrq().
> +	 */
> +	if (atomic) {
> +		if (unlikely(smp_processor_id() != cpu))
> +			return -EIO;

This series breaks[1] our application[2] in cases where the reads are
issued from any available CPU it is scheduled on. This issue is not seen on
older platforms which use the original arch/x86 RAPL implementation.

Can someone please shed some light on the change of userspace expectations?
Or did I miss any points in the documentation?

[1] https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6935
[2] https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/lib/igt_power.c

Raag

> +		rdmsrq(ra->reg.msr, ra->value);
> +		goto out;
> +	}
> +
>  	if (rdmsrq_safe_on_cpu(cpu, ra->reg.msr, &ra->value)) {
>  		pr_debug("failed to read msr 0x%x on cpu %d\n", ra->reg.msr, cpu);
>  		return -EIO;
>  	}
> +
> +out:
>  	ra->value &= ra->mask;
>  	return 0;
>  }

  reply	other threads:[~2026-02-14  6:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  0:05 [PATCH v1 0/2] Add MSR-based RAPL PMU support Kuppuswamy Sathyanarayanan
2025-11-21  0:05 ` [PATCH v1 1/2] powercap: intel_rapl: Prepare read_raw interface for atomic-context callers Kuppuswamy Sathyanarayanan
2026-02-14  6:37   ` Raag Jadav [this message]
2026-02-14 15:31     ` Sathyanarayanan Kuppuswamy
2026-02-14 16:12       ` Raag Jadav
2025-11-21  0:05 ` [PATCH v1 2/2] powercap: intel_rapl: Enable MSR-based RAPL PMU support Kuppuswamy Sathyanarayanan
2025-11-21  1:49 ` [PATCH v1 0/2] Add " Pandruvada, Srinivas
2025-11-21 20:48   ` Rafael J. Wysocki

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=aZAYHb0kO8eS0Z_5@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=kamil.konieczny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=sk.anirban@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