Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210618145534.438816-1-sxwjean@me.com>
In-Reply-To: <20210618145534.438816-1-sxwjean@me.com>
From:   Xiongwei Song <sxwjean@gmail.com>
Date:   Mon, 12 Jul 2021 16:19:31 +0800
Message-ID: <CAEVVKH9W=O7aCfmkx=hwqHJ+-4wM_zSB0uG8n3PaXXbPptTPuw@mail.gmail.com>
Subject: Re: [PATCH v2 0/3] some improvements for lockdep
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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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
>