From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] locking changes for v6.3
Date: Mon, 20 Feb 2023 13:25:50 +0100 [thread overview]
Message-ID: <Y/NmzouehvMWTPVZ@gmail.com> (raw)
In-Reply-To: <Y5eMDYABnSszN9/s@gmail.com>
Linus,
Please pull the latest locking tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2023-02-20
# HEAD: 3b4863fa5b7dd50dab1b10abbed938efd203752f vduse: Remove include of rwlock.h
Updates for this cycle were:
- rwsem micro-optimizations
- spinlock micro-optimizations
- cleanups, simplifications
Thanks,
Ingo
------------------>
Guo Ren (1):
locking/qspinlock: Micro-optimize pending state waiting for unlock
Sebastian Andrzej Siewior (2):
locking/lockdep: Remove lockdep_init_map_crosslock.
vduse: Remove include of rwlock.h
Uros Bizjak (2):
x86/PAT: Use try_cmpxchg() in set_page_memtype()
x86/ACPI/boot: Use try_cmpxchg() in __acpi_{acquire,release}_global_lock()
Waiman Long (3):
locking/rwsem: Prevent non-first waiter from spinning in down_write() slowpath
locking/rwsem: Disable preemption in all down_read*() and up_read() code paths
locking/rwsem: Disable preemption in all down_write*() and up_write() code paths
arch/x86/kernel/acpi/boot.c | 16 +++----
arch/x86/mm/pat/memtype.c | 4 +-
drivers/vdpa/vdpa_user/iova_domain.h | 1 -
include/linux/lockdep.h | 1 -
kernel/locking/qspinlock.c | 4 +-
kernel/locking/rwsem.c | 87 +++++++++++++++++++++---------------
6 files changed, 64 insertions(+), 49 deletions(-)
next prev parent reply other threads:[~2023-02-20 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:16 [GIT PULL] locking changes for v6.2 Ingo Molnar
2022-12-12 23:45 ` pr-tracker-bot
2023-02-20 12:25 ` Ingo Molnar [this message]
2023-02-21 1:52 ` [GIT PULL] locking changes for v6.3 pr-tracker-bot
2023-04-27 19:58 ` [GIT PULL] locking changes for v6.4 Ingo Molnar
2023-04-28 21:40 ` Linus Torvalds
2023-04-29 6:47 ` Ingo Molnar
2023-05-04 17:28 ` Andrzej Hajda
2023-05-04 18:23 ` Linus Torvalds
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=Y/NmzouehvMWTPVZ@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--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 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.