From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-mm <linux-mm@kvack.org>, Andi Kleen <andi@firstfloor.org>,
Christoph Hellwig <hch@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Roland McGrath <roland@hack.frob.com>,
Thomas Gleixner <tglx@linutronix.de>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Anton Arapov <anton@redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH v9 3.2 0/9] Uprobes patchset with perf probe support
Date: Mon, 16 Jan 2012 20:47:55 +0530 [thread overview]
Message-ID: <20120116151755.GH10189@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120116083442.GA23622@elte.hu>
* Ingo Molnar <mingo@elte.hu> [2012-01-16 09:34:42]:
>
> * Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:
>
> > This patchset implements Uprobes which enables you to
> > dynamically probe any routine in a user space application and
> > collect information non-disruptively.
>
> Did all review feedback get addressed in your latest tree?
I think this question would be better answered by Peter, Oleg and
Masami. For my part, I have fixed all comments till now. Also uprobes
has been part of -next for quite sometime.
>
> If yes then it would be nice to hear the opinion of Andrew about
> this bit:
>
> > mm/mmap.c | 33 +-
>
> The relevant portion of the patch is:
>
> > --- a/mm/mmap.c
> > +++ b/mm/mmap.c
> > @@ -30,6 +30,7 @@
> > #include <linux/perf_event.h>
> > #include <linux/audit.h>
> > #include <linux/khugepaged.h>
> > +#include <linux/uprobes.h>
> >
> > #include <asm/uaccess.h>
> > #include <asm/cacheflush.h>
> > @@ -616,6 +617,13 @@ again: remove_next = 1 + (end > next->vm_end);
> > if (mapping)
> > mutex_unlock(&mapping->i_mmap_mutex);
> >
> > + if (root) {
> > + mmap_uprobe(vma);
> > +
> > + if (adjust_next)
> > + mmap_uprobe(next);
> > + }
> > +
> > if (remove_next) {
> > if (file) {
> > fput(file);
> > @@ -637,6 +645,8 @@ again: remove_next = 1 + (end > next->vm_end);
> > goto again;
> > }
> > }
> > + if (insert && file)
> > + mmap_uprobe(insert);
> >
> > validate_mm(mm);
> >
> > @@ -1329,6 +1339,11 @@ unsigned long mmap_region(struct file *file, unsigned long addr,
> > mm->locked_vm += (len >> PAGE_SHIFT);
> > } else if ((flags & MAP_POPULATE) && !(flags & MAP_NONBLOCK))
> > make_pages_present(addr, addr + len);
> > +
> > + if (file && mmap_uprobe(vma))
> > + /* matching probes but cannot insert */
> > + goto unmap_and_free_vma;
> > +
> > return addr;
> >
> > unmap_and_free_vma:
> > @@ -2305,6 +2320,10 @@ int insert_vm_struct(struct mm_struct * mm, struct vm_area_struct * vma)
> > if ((vma->vm_flags & VM_ACCOUNT) &&
> > security_vm_enough_memory_mm(mm, vma_pages(vma)))
> > return -ENOMEM;
> > +
> > + if (vma->vm_file && mmap_uprobe(vma))
> > + return -EINVAL;
> > +
> > vma_link(mm, vma, prev, rb_link, rb_parent);
> > return 0;
> > }
> > @@ -2356,6 +2375,10 @@ struct vm_area_struct *copy_vma(struct vm_area_struct **vmap,
> > new_vma->vm_pgoff = pgoff;
> > if (new_vma->vm_file) {
> > get_file(new_vma->vm_file);
> > +
> > + if (mmap_uprobe(new_vma))
> > + goto out_free_mempol;
> > +
> > if (vma->vm_flags & VM_EXECUTABLE)
> > added_exe_file_vma(mm);
> > }
>
> it's named mmap_uprobe(), which makes it rather single-purpose.
> The uprobes code wants to track vma life-time so that it can
> manage uprobes breakpoints installed here, correct?
>
Yes,
> We already have some other vma tracking goodies in perf itself
> (see perf_event_mmap() et al) - would it make sense to merge the
> two vma instrumentation facilities and not burden mm/ with two
> separate sets of callbacks?
Atleast for file backed vmas, perf_event_mmap seems to be interested in
just the new vma creations. Uprobes would also be interested in the size
changes like the vma growing/shrinking/remap. Is perf_event_mmap
interested in such changes? From what i could see, perf_event_mmap seems
to be interested in stack vma size changes but not file vma size
changes.
Also mmap_uprobe gets called in fork path. Currently we have a hook in
copy_mm/dup_mm so that we get to know the context of each vma that gets
added to the child and add its breakpoints. At dup_mm/dup_mmap we would
have taken mmap_sem for both parent and child so there is no way we
could have missed a register/unregister in the parent not reflected in
the child.
I see the perf_event_fork but that would have to enhanced to do a lot
more to help us do a mmap_uprobe.
>
> If all such issues are resolved then i guess we could queue up
> uprobes in -tip, conditional on it remaining sufficiently
> regression-, problem- and NAK-free.
Okay. Accepting uprobes into tip, would provide more testing/feedback.
>
> Also, it would be nice to hear Arnaldo's opinion about the
> tools/perf/ bits.
Whatever comments Arnaldo/Masami have given till now have been resolved.
--
Thanks and Regards
Srikar
next prev parent reply other threads:[~2012-01-16 15:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 11:48 [PATCH v9 3.2 0/9] Uprobes patchset with perf probe support Srikar Dronamraju
2012-01-10 11:48 ` [PATCH v9 3.2 1/9] uprobes: Install and remove breakpoints Srikar Dronamraju
2012-01-25 14:39 ` Denys Vlasenko
2012-01-25 16:31 ` Oleg Nesterov
2012-01-25 15:13 ` Denys Vlasenko
2012-01-25 15:32 ` Denys Vlasenko
2012-01-26 14:14 ` Masami Hiramatsu
2012-01-26 18:28 ` Denys Vlasenko
2012-01-30 9:51 ` Masami Hiramatsu
2012-01-26 13:38 ` Masami Hiramatsu
2012-01-26 13:45 ` Masami Hiramatsu
2012-01-10 11:48 ` [PATCH v9 3.2 2/9] uprobes: handle breakpoint and signal step exception Srikar Dronamraju
2012-01-18 8:39 ` Anton Arapov
2012-01-18 9:02 ` Srikar Dronamraju
2012-01-18 10:18 ` Mike Frysinger
2012-01-18 10:47 ` Srikar Dronamraju
2012-01-18 11:01 ` Mike Frysinger
2012-01-20 22:57 ` Mike Frysinger
2012-01-25 8:12 ` Srikar Dronamraju
2012-01-10 11:48 ` [PATCH v9 3.2 3/9] uprobes: slot allocation Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 4/9] uprobes: counter to optimize probe hits Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 5/9] tracing: modify is_delete, is_return from ints to bool Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 6/9] tracing: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface Srikar Dronamraju
2012-01-16 13:11 ` Jiri Olsa
2012-01-16 14:45 ` Srikar Dronamraju
2012-01-16 15:33 ` Jiri Olsa
2012-01-16 16:41 ` Srikar Dronamraju
2012-01-17 9:28 ` Ingo Molnar
2012-01-17 10:22 ` Srikar Dronamraju
2012-01-17 10:59 ` Ingo Molnar
2012-01-17 11:03 ` Srikar Dronamraju
2012-01-17 11:22 ` Ingo Molnar
2012-01-17 11:57 ` Srikar Dronamraju
2012-01-17 12:23 ` Ingo Molnar
2012-01-17 12:27 ` Ingo Molnar
2012-01-17 12:11 ` Ingo Molnar
2012-01-17 12:21 ` Ingo Molnar
2012-01-18 10:07 ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 8/9] perf: rename target_module to target Srikar Dronamraju
2012-01-16 8:34 ` [PATCH v9 3.2 0/9] Uprobes patchset with perf probe support Ingo Molnar
2012-01-16 15:17 ` Srikar Dronamraju [this message]
2012-01-17 9:39 ` Ingo Molnar
2012-01-25 14:11 ` Peter Zijlstra
2012-01-26 11:10 ` 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=20120116151755.GH10189@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--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=roland@hack.frob.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).