All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jason Baron <jbaron@redhat.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, paulus@samba.org,
	rostedt@goodmis.org, fweisbec@gmail.com
Subject: Re: [PATCH 2/2] perf_counter: add support to the 'perf' tool for tracepoints
Date: Tue, 07 Jul 2009 10:29:20 +0200	[thread overview]
Message-ID: <1246955360.8143.113.camel@twins> (raw)
In-Reply-To: <0d7326e18b9860fbf8fb2739f90a23eb9262e24b.1246912068.git.jbaron@redhat.com>

On Mon, 2009-07-06 at 17:12 -0400, Jason Baron wrote:
> Add support to 'perf list' and 'perf stat' for kernel tracepoints. The
> implementation creates a 'for_each_subsystem' and 'for_each_event' for
> easy iteration over the tracepoints. The debugfs filesystem must be mounted
> at '/sys/kernel/debug'. We can add an optional search path in the future.

I don't have a single machine that has that mount point.



  reply	other threads:[~2009-07-07  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 21:11 [PATCH 0/2] perf_counter: add tracepoint support Jason Baron
2009-07-06 21:11 ` [PATCH 1/2] perf_counter: cleanup kernel perf counter support for tracepoints Jason Baron
2009-07-06 21:12 ` [PATCH 2/2] perf_counter: add support to the 'perf' tool " Jason Baron
2009-07-07  8:29   ` Peter Zijlstra [this message]
2009-07-08 20:17     ` [PATCH 3/2] perf_counters: add debugfs dir option Jason Baron
2009-07-09  0:47       ` Frederic Weisbecker
2009-07-09 14:45         ` Jason Baron
2009-07-10  4:17           ` Ingo Molnar
2009-07-13  7:15   ` [PATCH 2/2] perf_counter: add support to the 'perf' tool for tracepoints Ingo Molnar
2009-07-09  3:10 ` [PATCH 0/2] perf_counter: add tracepoint support Frederic Weisbecker
2009-07-09  7:58   ` Peter Zijlstra
2009-07-10  3:53     ` Ingo Molnar

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=1246955360.8143.113.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=rostedt@goodmis.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.