From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, Borislav Petkov <bp@alien8.de>
Subject: [GIT PULL] locking changes for v6.10
Date: Mon, 13 May 2024 08:04:04 +0200 [thread overview]
Message-ID: <ZkGtVO7uhcFXEeX6@gmail.com> (raw)
Linus,
Please pull the latest locking/core Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2024-05-13
# HEAD: 532453e7aa78f3962fb4d86caf40ff81ebf62160 locking/pvqspinlock/x86: Use _Q_LOCKED_VAL in PV_UNLOCK_ASM macro
Locking changes for v6.10:
- Over a dozen code generation micro-optimizations for the atomic
and spinlock code.
- Add more __ro_after_init attributes
- Robustify the lockdevent_*() macros
Thanks,
Ingo
------------------>
Peter Zijlstra (1):
jump_label,module: Don't alloc static_key_mod for __ro_after_init keys
Uros Bizjak (15):
locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128()
locking/atomic/x86: Modernize x86_32 arch_{,try_}_cmpxchg64{,_local}()
locking/atomic/x86: Introduce arch_try_cmpxchg64() for !CONFIG_X86_CMPXCHG64
locking/atomic/x86: Introduce arch_atomic64_try_cmpxchg() to x86_32
locking/atomic/x86: Introduce arch_atomic64_read_nonatomic() to x86_32
locking/atomic/x86: Rewrite x86_32 arch_atomic64_{,fetch}_{and,or,xor}() functions
locking/atomic/x86: Define arch_atomic_sub() family using arch_atomic_add() functions
locking/qspinlock: Use atomic_try_cmpxchg_relaxed() in xchg_tail()
locking/pvqspinlock: Use try_cmpxchg_acquire() in trylock_clear_pending()
locking/pvqspinlock: Use try_cmpxchg() in qspinlock_paravirt.h
locking/pvqspinlock/x86: Remove redundant CMP after CMPXCHG in __raw_callee_save___pv_queued_spin_unlock()
locking/atomic/x86: Introduce arch_try_cmpxchg64_local()
locking/atomic/x86: Merge __arch{,_try}_cmpxchg64_emu_local() with __arch{,_try}_cmpxchg64_emu()
locking/qspinlock/x86: Micro-optimize virt_spin_lock()
locking/pvqspinlock/x86: Use _Q_LOCKED_VAL in PV_UNLOCK_ASM macro
Valentin Schneider (3):
context_tracking: Make context_tracking_key __ro_after_init
x86/kvm: Make kvm_async_pf_enabled __ro_after_init
x86/tsc: Make __use_tsc __ro_after_init
Waiman Long (1):
locking/qspinlock: Always evaluate lockevent* non-event parameter once
arch/x86/include/asm/atomic.h | 12 +-
arch/x86/include/asm/atomic64_32.h | 79 +++++++----
arch/x86/include/asm/atomic64_64.h | 12 +-
arch/x86/include/asm/cmpxchg_32.h | 209 ++++++++++++++++++------------
arch/x86/include/asm/cmpxchg_64.h | 8 +-
arch/x86/include/asm/qspinlock.h | 13 +-
arch/x86/include/asm/qspinlock_paravirt.h | 7 +-
arch/x86/kernel/kvm.c | 2 +-
arch/x86/kernel/tsc.c | 2 +-
include/asm-generic/sections.h | 5 +
include/linux/jump_label.h | 3 +
init/main.c | 1 +
kernel/context_tracking.c | 2 +-
kernel/jump_label.c | 53 ++++++++
kernel/locking/lock_events.h | 4 +-
kernel/locking/qspinlock.c | 13 +-
kernel/locking/qspinlock_paravirt.h | 49 ++++---
17 files changed, 297 insertions(+), 177 deletions(-)
next reply other threads:[~2024-05-13 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 6:04 Ingo Molnar [this message]
2024-05-14 2:51 ` [GIT PULL] locking changes for v6.10 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=ZkGtVO7uhcFXEeX6@gmail.com \
--to=mingo@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).