From: Peter Zijlstra <peterz@infradead.org>
To: greearb@candelatech.com
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] lockdep: Change __lock_acquire to __lock_acquire_lockdep
Date: Thu, 10 May 2018 10:32:52 +0200 [thread overview]
Message-ID: <20180510083252.GX12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1525900482-31661-1-git-send-email-greearb@candelatech.com>
On Wed, May 09, 2018 at 02:14:42PM -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> This should make it easier to notice one is using lockdep when
> looking at 'perf top' and related output.
But you know now.. also, teach your benchmark scripts to complain if
/proc/lockdep exists.
prev parent reply other threads:[~2018-05-10 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:14 greearb
2018-05-10 8:32 ` Peter Zijlstra [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=20180510083252.GX12217@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 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®