public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	x86@kernel.org, qiuxu.zhuo@intel.com
Subject: Re: [GIT pull] x86/urgent for v6.11-rc3
Date: Tue, 13 Aug 2024 19:33:00 +0200	[thread overview]
Message-ID: <87o75wpbub.ffs@tglx> (raw)
In-Reply-To: <20240813031522.4544-1-qiuxu.zhuo@intel.com>

On Tue, Aug 13 2024 at 11:15, Qiuxu Zhuo wrote:
>> From: Thomas Gleixner <tglx@linutronix.de>
>> On Sun, Aug 11 2024 at 11:07, Linus Torvalds wrote:
>> > I doubt it actually matters, since I think this all is fundamentally
>> > just in the slow-path, so the "do a branch or a no-op" is likely
>> > entirely in the noise even if I followed the code right. But it looked
>> > off to me.
>> 
>> It is off and yes it won't matter much in the slowpath maze.
>
> static_branch_unlikely() matches that 'virt_spin_lock_key' is set to false 
> in default after the commit,
>
>   e639222a5119 ("x86/paravirt: Fix incorrect virt spinlock setting on bare metal")
>   
> although it offers little performance benefit since it is in the slow path.
>
> Thomas, do you think it's worth making a patch to convert static_branch_likely()
> to static_branch_unlikely() for this check, as suggested by Linus?
> If so, I can assist with this.

Sure, but I'm not so sure that it actually matters and makes a
measurable difference.

Thanks,

        tglx

  reply	other threads:[~2024-08-13 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 13:58 [GIT pull] irq/urgent for v6.11-rc3 Thomas Gleixner
2024-08-11 13:58 ` [GIT pull] timers/urgent " Thomas Gleixner
2024-08-11 18:22   ` pr-tracker-bot
2024-08-11 13:58 ` [GIT pull] x86/urgent " Thomas Gleixner
2024-08-11 17:30   ` Linus Torvalds
2024-08-12  8:04     ` Thomas Gleixner
2024-08-11 18:07   ` Linus Torvalds
2024-08-12  8:21     ` Thomas Gleixner
2024-08-13  3:15       ` Qiuxu Zhuo
2024-08-13 17:33         ` Thomas Gleixner [this message]
2024-08-14  3:14           ` [PATCH 1/1] x86/paravirt: Use static_branch_unlikely() for virt_spin_lock_key test Qiuxu Zhuo
2024-08-11 18:22   ` [GIT pull] x86/urgent for v6.11-rc3 pr-tracker-bot
2024-08-11 18:22 ` [GIT pull] irq/urgent " pr-tracker-bot

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=87o75wpbub.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=torvalds@linux-foundation.org \
    --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