From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH -tip 1/4] x86/idle: Fix argument type for MONITOR{,X} and MWAIT{,X} instructions
Date: Wed, 2 Apr 2025 22:48:11 +0200 [thread overview]
Message-ID: <Z-2ii-KgGSsMMTvB@gmail.com> (raw)
In-Reply-To: <20250402180827.3762-1-ubizjak@gmail.com>
* Uros Bizjak <ubizjak@gmail.com> wrote:
> MONITOR and MONITORX expect 32-bit unsigned integer argument in %ecx
> and %edx registers. MWAIT and MWAITX expect 32-bit usigned int
> argument in %eax and %ecx registers.
Please always include a 0/4 cover letter as well for such series, which
gives people a chance to reply to the whole series, instead of having
to awkwardly pick a patch to reply to. :-)
Such as this general feedback:
I've applied this series with edits to the changelogs, note in
particular:
patch #1:
- Changed verbiage from 'fix' to 'standardize to u32'. There was no
bug to fix, using 'long' instead of 'int' is at worst an ineffiency.
patch #3:
- Provided much needed historic context behind ;, \t, \n beautifiers
used in asm() statements. These aren't just random noise added in.
patch #4:
- Added in the current binutils version cutoff, to make it really
clear why we cannot use the mnemonic yet, and how far away we are
from doing so.
I've also extended the Cc: list in the commit to give people a chance
to object, to patch #3 in particular:
8ad521aaf743 ("x86/idle: Remove .s output beautifying delimiters from simpler asm() templates")
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-02 20:48 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
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 ` Ingo Molnar [this message]
2025-04-02 21:18 ` [PATCH -tip 1/4] x86/idle: Fix argument type for MONITOR{,X} and MWAIT{,X} instructions 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-2ii-KgGSsMMTvB@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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