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 -tip 2/2] x86/hweight: Use POPCNT when available with X86_NATIVE_CPU option
Date: Sun, 30 Mar 2025 20:47:31 +0200 [thread overview]
Message-ID: <Z-mRwxb3r1yrH332@gmail.com> (raw)
In-Reply-To: <20250330173140.GCZ-l__PVdSx6mj-zL@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Sun, Mar 30, 2025 at 05:15:16PM +0200, Uros Bizjak wrote:
> > You missed this part:
> >
> > --q--
> > ... where there is no need for an entry in the .altinstr_replacement
>
> Not really - .altinstr* memory gets jettisoned after boot.
>
> > section, shrinking all text sections by 9476 bytes:
>
> So if anything, this saves a whopping ~9K disk space and makes
> hweight* an unreadable mess.
What unreadable mess?
The proposed patch is:
+#ifdef __POPCNT__
+ asm_inline (ASM_FORCE_CLR "popcntl %[val], %[cnt]"
+ : [cnt] "=&r" (res)
+ : [val] ASM_INPUT_RM (w));
+#else
asm_inline (ALTERNATIVE(ANNOTATE_IGNORE_ALTERNATIVE
"call __sw_hweight32",
ASM_CLR "popcntl %[val], %[cnt]",
X86_FEATURE_POPCNT)
: [cnt] "=a" (res), ASM_CALL_CONSTRAINT
: [val] REG_IN (w));
-
+#endif
Which is 3 straightforward lines of assembly code and a straightforward #ifdef.
My main objection is different: if __POPCNT__ isn't defined during the
kernel build of major Linux distros, then this optimization almost
doesn't exist to our users. And I don't think it's defined.
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-30 18:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 16:48 [PATCH -tip 1/2] x86/hweight: Fix false output register dependency of POPCNT insn Uros Bizjak
2025-03-25 16:48 ` [PATCH -tip 2/2] x86/hweight: Use POPCNT when available with X86_NATIVE_CPU option Uros Bizjak
2025-03-25 17:11 ` Borislav Petkov
2025-03-30 15:15 ` Uros Bizjak
2025-03-30 17:31 ` Borislav Petkov
2025-03-30 18:47 ` Ingo Molnar [this message]
2025-03-30 19:06 ` Borislav Petkov
2025-03-30 19:20 ` Ingo Molnar
2025-03-30 19:28 ` Borislav Petkov
2025-03-25 21:56 ` Ingo Molnar
2025-03-29 9:19 ` Uros Bizjak
2025-03-29 11:00 ` David Laight
2025-03-30 7:49 ` Uros Bizjak
2025-03-30 18:02 ` David Laight
2025-03-29 23:10 ` H. Peter Anvin
2025-03-30 6:54 ` Uros Bizjak
2025-03-30 9:56 ` Ingo Molnar
2025-03-30 16:07 ` Uros Bizjak
2025-03-30 18:15 ` David Laight
2025-03-30 22:44 ` H. Peter Anvin
2025-03-30 18:54 ` Ingo Molnar
2025-03-25 17:09 ` [PATCH -tip 1/2] x86/hweight: Fix false output register dependency of POPCNT insn Borislav Petkov
2025-03-25 17:17 ` Uros Bizjak
2025-03-25 17:44 ` Borislav Petkov
2025-03-25 21:50 ` 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=Z-mRwxb3r1yrH332@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.