From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: [PATCH v3 0/3] locking/lockdep: Disable KASAN instrumentation of lockdep.c
Date: Sun, 9 Feb 2025 23:26:09 -0500 [thread overview]
Message-ID: <20250210042612.978247-1-longman@redhat.com> (raw)
v3:
- Add another patch to insert lock events into lockdep.c.
- Rerun all the tests with the simpler defconfig kernel build and do
further analysis of the of the performance difference between the
the RT and non-RT debug kernels.
It is found that disabling KASAN instrumentation when compiling
lockdep.c can significantly improve the performance of RT debug kernel
while the performance benefit of non-RT debug kernel is relatively
modest.
This series also include patches to add locking events to the rtmutex
slow paths and the lockdep code for better analysis of the different
performance behavior between RT and non-RT debug kernels.
Waiman Long (3):
locking/lock_events: Add locking events for rtmutex slow paths
locking/lock_events: Add locking events for lockdep
locking/lockdep: Disable KASAN instrumentation of lockdep.c
kernel/locking/Makefile | 3 ++-
kernel/locking/lock_events_list.h | 28 ++++++++++++++++++++++++++++
kernel/locking/lockdep.c | 8 +++++++-
kernel/locking/rtmutex.c | 29 ++++++++++++++++++++++++-----
4 files changed, 61 insertions(+), 7 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-10 4:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 4:26 Waiman Long [this message]
2025-02-10 4:26 ` [PATCH v3 1/3] locking/lock_events: Add locking events for rtmutex slow paths Waiman Long
2025-02-10 4:26 ` [PATCH v3 2/3] locking/lock_events: Add locking events for lockdep Waiman Long
2025-02-10 4:26 ` [PATCH v3 3/3] locking/lockdep: Disable KASAN instrumentation of lockdep.c Waiman Long
2025-02-12 5:57 ` Boqun Feng
2025-02-12 11:30 ` Marco Elver
2025-02-12 16:57 ` Waiman Long
2025-02-13 20:06 ` Waiman Long
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=20250210042612.978247-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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.