Linux Power Management development
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-hwmon@vger.kernel.org, linux-pm@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Guenter Roeck <linux@roeck-us.net>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH v2 07/10] x86/msr: Switch rdmsr_safe_on_cpu() users to rdmsrq_safe_on_cpu()
Date: Sat, 6 Jun 2026 11:51:26 +0200	[thread overview]
Message-ID: <aiPtnrkdHDHc0Iqz@gmail.com> (raw)
In-Reply-To: <20260605144314.3031049-8-jgross@suse.com>


* Juergen Gross <jgross@suse.com> wrote:

> In order to prepare retiring rdmsr_safe_on_cpu() switch
> rdmsr_safe_on_cpu() users to rdmsrq_safe_on_cpu().

> --- a/arch/x86/lib/msr-smp.c
> +++ b/arch/x86/lib/msr-smp.c
> @@ -190,11 +190,22 @@ EXPORT_SYMBOL(wrmsrq_safe_on_cpu);
>  
>  int rdmsrq_safe_on_cpu(unsigned int cpu, u32 msr_no, u64 *q)
>  {
> -	u32 low, high;
> +	struct msr_info_completion rv;
> +	call_single_data_t csd;
>  	int err;
>  
> -	err = rdmsr_safe_on_cpu(cpu, msr_no, &low, &high);
> -	*q = (u64)high << 32 | low;
> +	INIT_CSD(&csd, __rdmsr_safe_on_cpu, &rv);
> +
> +	memset(&rv, 0, sizeof(rv));
> +	init_completion(&rv.done);
> +	rv.msr.msr_no = msr_no;
> +
> +	err = smp_call_function_single_async(cpu, &csd);
> +	if (!err) {
> +		wait_for_completion(&rv.done);
> +		err = rv.msr.err;
> +	}
> +	*q = rv.msr.reg.q;

While technically this is another API user conversion,
I'd split this out into another preparatory patch,
because this changes the API itself.

Thanks,

	Ingo


  parent reply	other threads:[~2026-06-06  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 14:43 [PATCH v2 00/10] x86/msr: Drop 32-bit variants of *_on_cpu() MSR functions Juergen Gross
2026-06-05 14:43 ` [PATCH v2 01/10] x86/msr: Switch rdmsrl_on_cpu() users to rdmsrq_on_cpu() Juergen Gross
2026-06-05 14:43 ` [PATCH v2 03/10] x86/msr: Switch rdmsr_on_cpu() " Juergen Gross
2026-06-05 14:43 ` [PATCH v2 05/10] x86/msr: Switch wrmsr_on_cpu() users to wrmsrq_on_cpu() Juergen Gross
2026-06-05 14:43 ` [PATCH v2 07/10] x86/msr: Switch rdmsr_safe_on_cpu() users to rdmsrq_safe_on_cpu() Juergen Gross
2026-06-05 15:04   ` Dave Hansen
2026-06-06  9:51   ` Ingo Molnar [this message]
2026-06-05 14:43 ` [PATCH v2 09/10] x86/msr: Switch wrmsr_safe_on_cpu() users to wrmsrq_safe_on_cpu() Juergen Gross
2026-06-05 15:08 ` [PATCH v2 00/10] x86/msr: Drop 32-bit variants of *_on_cpu() MSR functions Dave Hansen
2026-06-05 15:09   ` Jürgen Groß

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=aiPtnrkdHDHc0Iqz@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=daniel.lezcano@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lukasz.luba@arm.com \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox