public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH] locking/pvqspinlock/x86: Use _Q_LOCKED_VAL in PV_UNLOCK_ASM macro
Date: Mon, 22 Apr 2024 13:00:39 -0700	[thread overview]
Message-ID: <ZibB5zp5DcCmC9gP@boqun-archlinux> (raw)
In-Reply-To: <CAFULd4ZhTAY9irw8V=MLZpjQK+q0AM_Aw8g2E=ivHjv7+5m9Zg@mail.gmail.com>

On Mon, Apr 22, 2024 at 09:57:04PM +0200, Uros Bizjak wrote:
> On Mon, Apr 22, 2024 at 9:45 PM Boqun Feng <boqun.feng@gmail.com> wrote:
> 
> > > diff --git a/arch/x86/include/asm/qspinlock_paravirt.h b/arch/x86/include/asm/qspinlock_paravirt.h
> > > index 466af57b8ed6..0a985784be9b 100644
> > > --- a/arch/x86/include/asm/qspinlock_paravirt.h
> > > +++ b/arch/x86/include/asm/qspinlock_paravirt.h
> > > @@ -40,7 +40,7 @@ __PV_CALLEE_SAVE_REGS_THUNK(__pv_queued_spin_unlock_slowpath, ".spinlock.text");
> > >  #define PV_UNLOCK_ASM                                                        \
> > >       FRAME_BEGIN                                                     \
> > >       "push  %rdx\n\t"                                                \
> > > -     "mov   $0x1,%eax\n\t"                                           \
> > > +     "mov   $" __stringify(_Q_LOCKED_VAL) ",%eax\n\t"                \
> > >       "xor   %edx,%edx\n\t"                                           \
> > >       LOCK_PREFIX "cmpxchg %dl,(%rdi)\n\t"                            \
> > >       "jne   .slowpath\n\t"                                           \
> >
> > There is also a "cmp $0x1,%al" afterwards.
> 
> Not anymore. Please note that the patch is against -tip, where we have:
> 

Oh, thanks for the information. Maybe it makes sense to mention the
patches dependency in the commit log?

Regards,
Boqun

> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=91095666125a666c8f20c2323b742c53165c0325
> 
> Thanks,
> Uros.

  reply	other threads:[~2024-04-22 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 15:17 [PATCH] locking/pvqspinlock/x86: Use _Q_LOCKED_VAL in PV_UNLOCK_ASM macro Uros Bizjak
2024-04-22 19:45 ` Boqun Feng
2024-04-22 19:57   ` Uros Bizjak
2024-04-22 20:00     ` Boqun Feng [this message]
2024-04-22 20:12       ` Uros Bizjak
2024-04-22 22:28         ` Boqun Feng
2024-04-24 10:04 ` [tip: locking/core] " 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=ZibB5zp5DcCmC9gP@boqun-archlinux \
    --to=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ubizjak@gmail.com \
    --cc=will@kernel.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