[lkml]   [2009]   [Sep]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: mailing list for trace users
On 09/16/2009 11:16 PM, Steven Rostedt wrote:
> What are people's thoughts about creating a linux-trace-users mailing
> list on
> This would be a place for users of tracers and even perf. For asking
> questions about how to use the debugfs/tracing directory or the perf
> tool.
> This will not be a place for kernel development. Patches for the tracing
> infrastructure should still go through LKML. This will be a place to ask
> how-to questions, or any other kind of help questions.
> LKML can be quite intimidating, and it is not a place to ask help
> questions anyway. I think adding a linux-trace-users mailing list would
> be a good idea.

Yes please. Here's a question to start it off - how to I 'perf
annotate' a symbol in a module?

$ perf report
# Samples: 68202
# Overhead Command Shared Object Symbol
# ........ ............... ............. ......
84.17% qemu-system-x86 [kernel] [k] vmx_vcpu_run [kvm_intel]
4.28% qemu-system-x86 [kernel] [k] kvm_arch_vcpu_ioctl_run
0.88% qemu-system-x86 [kernel] [k] add_preempt_count
0.75% qemu-system-x86 [kernel] [k] _spin_unlock_irqrestore
0.68% qemu-system-x86 [kernel] [k] _spin_lock_irq
$ perf annotate -k ~avi/kvm/linux-2.6/vmlinux -m vmx_vcpu_run
Error: symbol 'vmx_vcpu_run' not present amongst the samples.

builtin symbols work.

error compiling committee.c: too many arguments to function

 \ /
  Last update: 2009-09-22 11:15    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean