[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z9XxNbdLCZFiK1NG@gmail.com>
Date: Sat, 15 Mar 2025 22:29:25 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Uros Bizjak <ubizjak@...il.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/asm: Use alternative_input() in amd_clear_divider()
* Borislav Petkov <bp@...en8.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@...il.com>
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Cc: Ingo Molnar <mingo@...nel.org>
> > Cc: Borislav Petkov <bp@...en8.de>
> > Cc: Dave Hansen <dave.hansen@...ux.intel.com>
> > Cc: "H. Peter Anvin" <hpa@...or.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
Powered by blists - more mailing lists