All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-mm <linux-mm@kvack.org>, Oleg Nesterov <oleg@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH UPDATED 3/3] tracing: Provide trace events interface for uprobes
Date: Thu, 12 Apr 2012 20:19:27 +0530	[thread overview]
Message-ID: <20120412144927.GB21587@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F86D264.9020004@hitachi.com>

> > +
> > +    # echo 'p /bin/zsh:0x46420 %ip %ax' > uprobe_events
> > +
> > +Please note: User has to explicitly calculate the offset of the probepoint
> > +in the object. We can see the events that are registered by looking at the
> > +uprobe_events file.
> > +
> > +    # cat uprobe_events
> > +    p:uprobes/p_zsh_0x46420 /bin/zsh:0x0000000000046420
> 
> Doesn't uprobe_events show the arguments of existing events?
> And also, could you add an event format of above event here?
> 

[root@f14kvm tracing]#  cat uprobe_events 
[root@f14kvm tracing]# echo 'p /bin/zsh:0x46420 %ip %ax' > uprobe_events 
[root@f14kvm tracing]#  cat uprobe_events 
p:uprobes/p_zsh_0x46420 /bin/zsh:0x00046420 arg1=%ip arg2=%ax
[root@f14kvm tracing]#  cat events/uprobes/p_zsh_0x46420/format 
name: p_zsh_0x46420
ID: 922
format:
        field:unsigned short common_type;       offset:0;       size:2; signed:0;
        field:unsigned char common_flags;       offset:2;       size:1; signed:0;
        field:unsigned char common_preempt_count;       offset:3;       size:1; signed:0;
        field:int common_pid;   offset:4;       size:4; signed:1;
        field:int common_padding;       offset:8;       size:4; signed:1;

        field:unsigned long __probe_ip; offset:12;      size:4; signed:0;
        field:u32 arg1; offset:16;      size:4; signed:0;
        field:u32 arg2; offset:20;      size:4; signed:0;

print fmt: "(%lx) arg1=%lx arg2=%lx", REC->__probe_ip, REC->arg1, REC->arg2
[root@f14kvm tracing]# 

Will update the Documentation file  with correct output of "cat
uprobe_events". Do you want the format file to be added to the
Documentation?

-- 
Thanks and Regards
Srikar

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-mm <linux-mm@kvack.org>, Oleg Nesterov <oleg@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH UPDATED 3/3] tracing: Provide trace events interface for uprobes
Date: Thu, 12 Apr 2012 20:19:27 +0530	[thread overview]
Message-ID: <20120412144927.GB21587@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F86D264.9020004@hitachi.com>

> > +
> > +    # echo 'p /bin/zsh:0x46420 %ip %ax' > uprobe_events
> > +
> > +Please note: User has to explicitly calculate the offset of the probepoint
> > +in the object. We can see the events that are registered by looking at the
> > +uprobe_events file.
> > +
> > +    # cat uprobe_events
> > +    p:uprobes/p_zsh_0x46420 /bin/zsh:0x0000000000046420
> 
> Doesn't uprobe_events show the arguments of existing events?
> And also, could you add an event format of above event here?
> 

[root@f14kvm tracing]#  cat uprobe_events 
[root@f14kvm tracing]# echo 'p /bin/zsh:0x46420 %ip %ax' > uprobe_events 
[root@f14kvm tracing]#  cat uprobe_events 
p:uprobes/p_zsh_0x46420 /bin/zsh:0x00046420 arg1=%ip arg2=%ax
[root@f14kvm tracing]#  cat events/uprobes/p_zsh_0x46420/format 
name: p_zsh_0x46420
ID: 922
format:
        field:unsigned short common_type;       offset:0;       size:2; signed:0;
        field:unsigned char common_flags;       offset:2;       size:1; signed:0;
        field:unsigned char common_preempt_count;       offset:3;       size:1; signed:0;
        field:int common_pid;   offset:4;       size:4; signed:1;
        field:int common_padding;       offset:8;       size:4; signed:1;

        field:unsigned long __probe_ip; offset:12;      size:4; signed:0;
        field:u32 arg1; offset:16;      size:4; signed:0;
        field:u32 arg2; offset:20;      size:4; signed:0;

print fmt: "(%lx) arg1=%lx arg2=%lx", REC->__probe_ip, REC->arg1, REC->arg2
[root@f14kvm tracing]# 

Will update the Documentation file  with correct output of "cat
uprobe_events". Do you want the format file to be added to the
Documentation?

-- 
Thanks and Regards
Srikar


  reply	other threads:[~2012-04-12 14:57 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09  9:11 [PATCH 1/3] tracing: Modify is_delete, is_return from int to bool Srikar Dronamraju
2012-04-09  9:11 ` Srikar Dronamraju
2012-04-09  9:11 ` [PATCH 2/3] tracing: Extract out common code for kprobes/uprobes trace events Srikar Dronamraju
2012-04-09  9:11   ` Srikar Dronamraju
2012-04-12 12:47   ` Masami Hiramatsu
2012-04-12 12:47     ` Masami Hiramatsu
2012-05-08  4:08   ` [tip:perf/uprobes] tracing: Extract out common code for kprobes/ uprobes " tip-bot for Srikar Dronamraju
2012-05-08  4:08     ` tip-bot for Srikar Dronamraju
2012-04-09  9:11 ` [PATCH 3/3] tracing: Provide trace events interface for uprobes Srikar Dronamraju
2012-04-09  9:11   ` Srikar Dronamraju
2012-04-11 10:30   ` [PATCH UPDATED " Srikar Dronamraju
2012-04-11 10:30     ` Srikar Dronamraju
2012-04-12 13:02     ` Masami Hiramatsu
2012-04-12 13:02       ` Masami Hiramatsu
2012-04-12 14:49       ` Srikar Dronamraju [this message]
2012-04-12 14:49         ` Srikar Dronamraju
2012-04-13  2:28         ` Masami Hiramatsu
2012-04-13  2:28           ` Masami Hiramatsu
2012-04-12 13:14     ` Steven Rostedt
2012-04-12 13:14       ` Steven Rostedt
2012-04-14 11:12       ` Ingo Molnar
2012-04-14 11:12         ` Ingo Molnar
2012-04-16  9:22         ` Srikar Dronamraju
2012-04-16  9:22           ` Srikar Dronamraju
2012-04-20  9:57         ` Srikar Dronamraju
2012-04-20  9:57           ` Srikar Dronamraju
2012-05-08  4:09     ` [tip:perf/uprobes] " tip-bot for Srikar Dronamraju
2012-05-08  4:09       ` tip-bot for Srikar Dronamraju
2012-05-08  4:12     ` [PATCH UPDATED 3/3] " Ingo Molnar
2012-05-08  4:12       ` Ingo Molnar
2012-05-08  8:30       ` Peter Zijlstra
2012-05-08  8:30         ` Peter Zijlstra
2012-05-08  8:50         ` Srikar Dronamraju
2012-05-08  8:50           ` Srikar Dronamraju
2012-05-08  9:20           ` Ingo Molnar
2012-05-08  9:20             ` Ingo Molnar
2012-05-08  9:19             ` Srikar Dronamraju
2012-05-08  9:19               ` Srikar Dronamraju
2012-04-12 12:42 ` [PATCH 1/3] tracing: Modify is_delete, is_return from int to bool Masami Hiramatsu
2012-04-12 12:42   ` Masami Hiramatsu
2012-05-08  4:07 ` [tip:perf/uprobes] " tip-bot for Srikar Dronamraju
2012-05-08  4:07   ` tip-bot for Srikar Dronamraju

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=20120412144927.GB21587@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=anton@redhat.com \
    --cc=hch@infradead.org \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.