public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
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 2/2] x86/bitops: Fix false output register dependency of TZCNT insn
Date: Fri, 28 Mar 2025 23:27:59 +0100	[thread overview]
Message-ID: <Z-cib74Y1NjB4huZ@gmail.com> (raw)
In-Reply-To: <CAFULd4agDYNCJrQQ8bji09eGVJp1D46LH=fOpcfciza2qhKJfg@mail.gmail.com>


* Uros Bizjak <ubizjak@gmail.com> wrote:

> On Tue, Mar 25, 2025 at 10:43 PM Ingo Molnar <mingo@kernel.org> wrote:
> >
> >
> > * Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > > On Haswell and later Intel processors, the TZCNT instruction appears
> > > to have a false dependency on the destination register. Even though
> > > the instruction only writes to it, the instruction will wait until
> > > destination is ready before executing. This false dependency
> > > was fixed for Skylake (and later) processors.
> > >
> > > Fix false dependency by clearing the destination register first.
> > >
> > > The x86_64 defconfig object size increases by 4215 bytes:
> > >
> > >           text           data     bss      dec            hex filename
> > >       27342396        4642999  814852 32800247        1f47df7 vmlinux-old.o
> > >       27346611        4643015  814852 32804478        1f48e7e vmlinux-new.o
> >
> > Yeah, so Skylake was released in 2015, about a decade ago.
> >
> > So we'd be making the kernel larger for an unquantified
> > micro-optimization for CPUs that almost nobody uses anymore.
> > That's a bad trade-off.
> 
> Yes, 4.2k seems a bit excessive. OTOH, I'd not say that the issue is 
> a micro-optimization, it is bordering on the hardware bug.

Has this been quantified, and do we really care about the 
micro-performance of ~10-year old CPUs, especially at the
expense of modern CPUs?

Thanks,

	Ingo

  reply	other threads:[~2025-03-28 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 17:52 [PATCH 1/2] x86/bitops: Use TZCNT mnemonic in <asm/bitops.h> Uros Bizjak
2025-03-25 17:52 ` [PATCH 2/2] x86/bitops: Fix false output register dependency of TZCNT insn Uros Bizjak
2025-03-25 17:59   ` Borislav Petkov
2025-03-25 18:29   ` H. Peter Anvin
2025-03-25 21:43   ` Ingo Molnar
2025-03-26  8:46     ` Uros Bizjak
2025-03-28 22:27       ` Ingo Molnar [this message]
2025-03-29  8:48         ` Uros Bizjak
2025-03-25 21:48 ` [tip: x86/asm] x86/bitops: Use TZCNT mnemonic in <asm/bitops.h> tip-bot2 for 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-cib74Y1NjB4huZ@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