From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH -tip 2/4] x86/idle: Use MONITOR and MWAIT mnemonics in <asm/mwait.h>
Date: Thu, 3 Apr 2025 18:30:41 +0300 [thread overview]
Message-ID: <Z-6poX1TFKLKn4mB@black.fi.intel.com> (raw)
In-Reply-To: <Z-6pDGR0pQavVQfq@black.fi.intel.com>
On Thu, Apr 03, 2025 at 06:28:13PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 02, 2025 at 08:08:06PM +0200, Uros Bizjak wrote:
> > Current minimum required version of binutils is 2.25,
> > which supports MONITOR and MWAIT instruction mnemonics.
> >
> > Replace the byte-wise specification of MONITOR and
> > MWAIT with these proper mnemonics.
> >
> > No functional change intended.
>
> Hmm... Is it only me who gets these, please?
>
> In file included from acpi/cstate.c:18:
> asm/mwait.h:30:15: error: invalid operand for instruction
> 30 | asm volatile("monitor %0, %1, %2" :: "a" (eax), "c" (ecx), "d" (edx));
> | ^
> <inline asm>:1:16: note: instantiated into assembly here
> 1 | monitor %rax, %ecx, %edx
> | ^~~~~
> In file included from acpi/cstate.c:18:
> asm/mwait.h:95:15: error: instruction requires: Not 64-bit mode
> 95 | asm volatile("sti; mwait %0, %1" :: "a" (eax), "c" (ecx));
> | ^
> <inline asm>:1:7: note: instantiated into assembly here
> 1 | sti; mwait %eax, %ecx
> | ^
FWIW, revert fixes the issue.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-03 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 18:08 [PATCH -tip 1/4] x86/idle: Fix argument type for MONITOR{,X} and MWAIT{,X} instructions Uros Bizjak
2025-04-02 18:08 ` [PATCH -tip 2/4] x86/idle: Use MONITOR and MWAIT mnemonics in <asm/mwait.h> Uros Bizjak
2025-04-02 20:43 ` [tip: x86/mm] " tip-bot2 for Uros Bizjak
2025-04-03 15:28 ` [PATCH -tip 2/4] " Andy Shevchenko
2025-04-03 15:30 ` Andy Shevchenko [this message]
2025-04-03 15:33 ` Ingo Molnar
2025-04-03 15:41 ` Andy Shevchenko
2025-04-02 18:08 ` [PATCH -tip 3/4] x86/idle: Remove unneeded delimiters from asm templates Uros Bizjak
2025-04-02 20:43 ` [tip: x86/mm] x86/idle: Remove .s output beautifying delimiters from simpler asm() templates tip-bot2 for Uros Bizjak
2025-04-03 11:27 ` tip-bot2 for Uros Bizjak
2025-04-02 18:08 ` [PATCH -tip 4/4] x86/idle: Remove CONFIG_AS_TPAUSE Uros Bizjak
2025-04-02 20:43 ` [tip: x86/mm] " tip-bot2 for Uros Bizjak
2025-04-02 20:55 ` tip-bot2 for Uros Bizjak
2025-04-03 11:27 ` tip-bot2 for Uros Bizjak
2025-04-02 20:43 ` [tip: x86/mm] x86/idle: Standardize argument types for MONITOR{,X} and MWAIT{,X} instruction wrappers on 'u32' tip-bot2 for Uros Bizjak
2025-04-02 23:26 ` Andrew Cooper
2025-04-02 20:48 ` [PATCH -tip 1/4] x86/idle: Fix argument type for MONITOR{,X} and MWAIT{,X} instructions Ingo Molnar
2025-04-02 21:18 ` Uros Bizjak
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=Z-6poX1TFKLKn4mB@black.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.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