All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: mingo@redhat.com, peterz@infradead.org, paulus@samba.org,
	acme@ghostprotocols.net, penberg@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 7/7] perf: integrate liblockdep support into perf
Date: Sun, 03 Feb 2013 16:39:43 -0500	[thread overview]
Message-ID: <510ED91F.6050601@oracle.com> (raw)
In-Reply-To: <20130203110537.GB11739@gmail.com>

On 02/03/2013 06:05 AM, Ingo Molnar wrote:
> 
> * Sasha Levin <sasha.levin@oracle.com> wrote:
> 
>> liblockdep is simply userspace lockdep. We can use that to analyze and
>> verify the locking in perf.
>>
>> Usage is simple, to compile perf with liblockdep all that's needed it:
>>
>> 	make LIBLOCK=[path to liblockdep]
> 
> Nice idea.
> 
> I'd suggest to link it in directly, like we link in 
> libtraceevents.
> 
> Then it could be built via something like:
> 
>    make LOCKDEP=1
> 
> or so.
> 

Sounds good, I'll resend the series.


Thanks,
Sasha


  reply	other threads:[~2013-02-03 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 17:15 [PATCH v2 7/7] perf: integrate liblockdep support into perf Sasha Levin
2013-02-03 11:05 ` Ingo Molnar
2013-02-03 21:39   ` Sasha Levin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-01 16:47 [PATCH v2 1/7] liblockdep: wrap kernel/lockdep.c to allow usage from userspace Sasha Levin
2013-02-01 16:47 ` [PATCH v2 7/7] perf: integrate liblockdep support into perf Sasha Levin

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=510ED91F.6050601@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.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 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.