From: Xiongwei Song <sxwjean@gmail.com>
To: Xiongwei Song <sxwjean@me.com>
Cc: peterz@infradead.org, mingo@redhat.com, will@kernel.org,
longman@redhat.com, Boqun Feng <boqun.feng@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] some improvements for lockdep
Date: Mon, 12 Jul 2021 16:19:31 +0800 [thread overview]
Message-ID: <CAEVVKH9W=O7aCfmkx=hwqHJ+-4wM_zSB0uG8n3PaXXbPptTPuw@mail.gmail.com> (raw)
In-Reply-To: <20210618145534.438816-1-sxwjean@me.com>
Hi Peter,
Will you pick up this series?
Regards,
Xiongwei
On Fri, Jun 18, 2021 at 10:55 PM Xiongwei Song <sxwjean@me.com> wrote:
>
> From: Xiongwei Song <sxwjean@gmail.com>
>
> Unlikely the checks of return values of graph walk will improve the
> performance to some degree, patch 1 and patch 2 are for this.
>
> The patch 3 will print a warning after counting lock deps when hitting
> bfs errors.
>
> v2:
> * For patch 3, avoid to call lockdep_unlock() twice after counting deps.
> Please see https://lkml.org/lkml/2021/6/17/741.
>
> Xiongwei Song (3):
> locking/lockdep: Unlikely bfs_error() inside
> locking/lockdep: Unlikely conditons about BFS_RMATCH
> locking/lockdep: Print possible warning after counting deps
>
> kernel/locking/lockdep.c | 55 +++++++++++++++++++---------------------
> 1 file changed, 26 insertions(+), 29 deletions(-)
>
> --
> 2.30.2
>
prev parent reply other threads:[~2021-07-12 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 14:55 [PATCH v2 0/3] some improvements for lockdep Xiongwei Song
2021-06-18 14:55 ` [PATCH v2 1/3] locking/lockdep: Unlikely bfs_error() inside Xiongwei Song
2021-06-18 14:55 ` [PATCH v2 2/3] locking/lockdep: Unlikely conditons about BFS_RMATCH Xiongwei Song
2021-06-18 14:55 ` [PATCH v2 3/3] locking/lockdep: Print possible warning after counting deps Xiongwei Song
2021-06-24 8:03 ` Xiongwei Song
2021-06-24 13:45 ` Boqun Feng
2021-07-12 8:19 ` Xiongwei Song [this message]
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='CAEVVKH9W=O7aCfmkx=hwqHJ+-4wM_zSB0uG8n3PaXXbPptTPuw@mail.gmail.com' \
--to=sxwjean@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sxwjean@me.com \
--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 NNTP newsgroup(s).