From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Uros Bizjak <ubizjak@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/asm: Use alternative_input() in amd_clear_divider()
Date: Sat, 15 Mar 2025 22:29:25 +0100 [thread overview]
Message-ID: <Z9XxNbdLCZFiK1NG@gmail.com> (raw)
In-Reply-To: <20250314112018.GAZ9QQ8hPXt2Mk22cG@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Fri, Mar 14, 2025 at 09:14:38AM +0100, Uros Bizjak wrote:
> > Use higher-level API to declare assembly with alternatives.
> >
> > bloat-o-meter reports no code size changes.
> >
> > Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ingo Molnar <mingo@kernel.org>
> > Cc: Borislav Petkov <bp@alien8.de>
> > Cc: Dave Hansen <dave.hansen@linux.intel.com>
> > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > ---
> > arch/x86/include/asm/processor.h | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
>
> I'm getting tired of patches which cause unnecessary code churn. Please stop
> this. If it ain't broke, it doesn't need fixing!
So why does the higher level alternative_input() API exist? If it
shouldn't exist then we should remove it. If it exists, we should use
it consistently instead of open-coding its equivalent.
Cleanups like this, especially if they are clearly part of an effort to
improve x86 code generation in this area, are not 'code churn', why
would they be?
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-15 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 8:14 [PATCH] x86/asm: Use alternative_input() in amd_clear_divider() Uros Bizjak
2025-03-14 11:20 ` Borislav Petkov
2025-03-15 21:29 ` Ingo Molnar [this message]
2025-03-15 21:36 ` Borislav Petkov
2025-03-16 8:40 ` Uros Bizjak
2025-03-16 18:34 ` H. Peter Anvin
2025-03-15 19:08 ` H. Peter Anvin
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=Z9XxNbdLCZFiK1NG@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=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