Linux EDAC development
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-edac@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] x86/mce: Fix build warning after MSR-interface switch
Date: Fri, 17 Jul 2026 12:18:07 +0200	[thread overview]
Message-ID: <b0705c60-1eb7-440d-91fe-ad329bbe407e@suse.com> (raw)
In-Reply-To: <aln1vdH7dPKmh0kl@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1592 bytes --]

On 17.07.26 11:28, Ingo Molnar wrote:
> 
> * Juergen Gross <jgross@suse.com> wrote:
> 
>> The recent switch to 64-bit MSR interfaces introduced a build warning.
>>
>> Fix it.
>>
>> Fixes: cff219368bd0 ("x86/mce: Stop using 32-bit MSR interfaces")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202607031726.ZOwu4snu-lkp@intel.com/
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> Said patch is in tip only right now, so this patch could either be added
>> on top or be folded into the original patch.
>> ---
>>   arch/x86/kernel/cpu/mce/p5.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kernel/cpu/mce/p5.c b/arch/x86/kernel/cpu/mce/p5.c
>> index eb99f384d747..3c2b6cc918b1 100644
>> --- a/arch/x86/kernel/cpu/mce/p5.c
>> +++ b/arch/x86/kernel/cpu/mce/p5.c
>> @@ -44,7 +44,7 @@ noinstr void pentium_machine_check(struct pt_regs *regs)
>>   /* Set up machine check reporting for processors with Intel style MCE: */
>>   void intel_p5_mcheck_init(struct cpuinfo_x86 *c)
>>   {
>> -	u64 q;
>> +	u64 __maybe_unused q;
> 
> Could we just fix the API to always assign 'q', instead of this
> ugly & vague annotation?

q is always assigned. I believe the problem is that it is never read.

OTOH this problem can be fixed easily after patch 31 of this series. I can send
a V2 of patch 32 to just drop the assignment to q. This will be possible as
rdmsrq() will be a function then, and not a macro requiring a variable being
passed as parameter.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2026-07-17 10:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29  6:04 [PATCH 00/32] x86/msr: Drop 32-bit MSR interfaces Juergen Gross
2026-06-29  6:04 ` [PATCH 03/32] edac: Stop using " Juergen Gross
2026-06-30  1:50   ` Zhuo, Qiuxu
2026-07-02 10:15   ` [tip: x86/msr] EDAC: " tip-bot2 for Juergen Gross
2026-06-29  6:04 ` [PATCH 08/32] x86/mce: " Juergen Gross
2026-07-03 10:55   ` [PATCH] x86/mce: Fix build warning after MSR-interface switch Juergen Gross
2026-07-17  9:28     ` Ingo Molnar
2026-07-17 10:18       ` Jürgen Groß [this message]
2026-07-17 10:25         ` Ingo Molnar
2026-07-17 11:03           ` Jürgen Groß
2026-06-29  6:05 ` [PATCH 31/32] treewide: convert rdmsrq() from a macro to an inline function Juergen Gross
2026-06-29  6:52 ` [PATCH 00/32] x86/msr: Drop 32-bit MSR interfaces Arnd Bergmann
2026-06-29  7:01   ` Jürgen Groß
2026-06-29  8:06     ` Arnd Bergmann
2026-06-29  8:15       ` Jürgen Groß
2026-06-29  8:38         ` Arnd Bergmann
2026-06-30 20:06           ` H. Peter Anvin
2026-06-29 11:19       ` Ingo Molnar
2026-06-30 18:59         ` Sean Christopherson
2026-07-01  8:33           ` Jürgen Groß
2026-07-02 10:07           ` Ingo Molnar
2026-07-02 11:03             ` Juergen Gross
2026-07-17  9:38               ` Ingo Molnar

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=b0705c60-1eb7-440d-91fe-ad329bbe407e@suse.com \
    --to=jgross@suse.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --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