On Mon, 2010-09-06 at 17:12 -0400, Christoph Hellwig wrote:
quoted text
> On Mon, Sep 06, 2010 at 11:06:08PM +0200, Peter Zijlstra wrote:
> > > The other things is that perf currently only supports per-kernel pid
> > > recording, while we'd really need per Posix process, which may contain
> > > multiple threads for useful tracing of complex userspace applications.
> > > I also suspect that this will fit the uprobes model much better given
> > > that the probes will be in any given address space.
> > 
> > perf does report both:
> > 
> >          *      { u32                   pid, tid; } && PERF_SAMPLE_TID
> > 
> > the pid is the process id (thread group leader like) and tid is the
> > task/thread id.
> 
> It records both, but I haven't found a way to only record samples
> or trace things in a Posix Process.
> 
> E.g. perf record -p seems to be only per-thread, not per-process.
> If that has changes recently everything is fine of course.

Hrm, the record code seems to look up all threads for -p and use only a
single thread for -t, didn't actually try it though so it could be
borken.


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