From: David Ahern <dsahern@gmail.com>
To: acme@ghostprotocols.net, linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, peterz@infradead.org, fweisbec@gmail.com,
David Ahern <dsahern@gmail.com>
Subject: [PATCH 0/3] perf: working with multithreaded processes with named threads
Date: Thu, 22 Dec 2011 11:30:00 -0700 [thread overview]
Message-ID: <1324578603-12762-1-git-send-email-dsahern@gmail.com> (raw)
One bug fix plus a couple of enhancements to improve handling of
named threads.
David Ahern (3):
perf: fix comm for processes with named threads
perf: look up thread names for system wide profiling
perf script: look up thread using tid instead of pid
tools/perf/builtin-script.c | 2 +-
tools/perf/util/event.c | 112 ++++++++++++++++++++++++++++++++----------
2 files changed, 86 insertions(+), 28 deletions(-)
--
1.7.7.4
next reply other threads:[~2011-12-22 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 18:30 David Ahern [this message]
2011-12-22 18:30 ` [PATCH 1/3] perf: fix comm for processes with named threads David Ahern
2011-12-29 20:46 ` [tip:perf/core] perf tools: Fix " tip-bot for David Ahern
2011-12-22 18:30 ` [PATCH 2/3 v2] perf: look up thread names for system wide profiling David Ahern
2011-12-29 20:47 ` [tip:perf/core] perf tools: Look " tip-bot for David Ahern
2011-12-22 18:30 ` [PATCH 3/3] perf script: look up thread using tid instead of pid David Ahern
2011-12-29 20:48 ` [tip:perf/core] " tip-bot for David Ahern
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 17:43 [PATCH 0/3] perf: working with multithreaded processes with named threads David Ahern
2011-12-16 23:50 ` David Ahern
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=1324578603-12762-1-git-send-email-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.