From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] locking changes for v5.4
Date: Mon, 16 Sep 2019 13:41:10 +0200 [thread overview]
Message-ID: <20190916114110.GA128086@gmail.com> (raw)
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-for-linus
# HEAD: e57d143091f1c0b1a98140a4d2e63e113afb62c0 mutex: Fix up mutex_waiter usage
This cycle's changes were:
- Improve rwsem scalability
- Add uninitialized rwsem debugging check
- Reduce lockdep's stacktrace memory usage and add diagnostics
- Misc cleanups, code consolidation and constification
Thanks,
Ingo
------------------>
Bart Van Assche (4):
locking/lockdep: Make it clear that what lock_class::key points at is not modified
stacktrace: Constify 'entries' arguments
locking/lockdep: Reduce space occupied by stack traces
locking/lockdep: Report more stack trace statistics
Davidlohr Bueso (1):
locking/rwsem: Check for operations on an uninitialized rwsem
Mukesh Ojha (2):
locking/mutex: Make __mutex_owner static to mutex.c
locking/mutex: Use mutex flags macro instead of hard code
Peter Zijlstra (2):
locking/qspinlock,x86: Clarify virt_spin_lock_key
mutex: Fix up mutex_waiter usage
Waiman Long (1):
locking/rwsem: Make handoff writer optimistically spin on owner
arch/x86/include/asm/qspinlock.h | 15 ++++
include/linux/lockdep.h | 11 +--
include/linux/mutex.h | 25 +-----
include/linux/rwsem.h | 10 +++
include/linux/stacktrace.h | 4 +-
kernel/locking/lockdep.c | 159 ++++++++++++++++++++++++++++---------
kernel/locking/lockdep_internals.h | 9 ++-
kernel/locking/lockdep_proc.c | 8 +-
kernel/locking/mutex.c | 26 ++++++
kernel/locking/rwsem.c | 54 ++++++++++---
kernel/stacktrace.c | 4 +-
11 files changed, 241 insertions(+), 84 deletions(-)
next reply other threads:[~2019-09-16 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:41 Ingo Molnar [this message]
2019-09-17 1:00 ` 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=20190916114110.GA128086@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®