linux-kernel - Re: mailing list for trace users

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AB89520.2050900@redhat.com>
Date:	Tue, 22 Sep 2009 12:13:04 +0300
From:	Avi Kivity <avi@...hat.com>
To:	rostedt@...dmis.org
CC:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	postmaster@...r.kernel.org
Subject: Re: 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 vger.kernel.org?
>
> 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 
[kvm]
      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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/