public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Don Zickus <dzickus@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	acme@ghostprotocols.net, eranian@google.com
Subject: Re: [PATCH 1/2] perf: fix synthesizing mmaps for threads
Date: Wed, 5 Mar 2014 17:58:57 +0100	[thread overview]
Message-ID: <20140305165857.GA28127@krava.brq.redhat.com> (raw)
In-Reply-To: <1393429527-167840-2-git-send-email-dzickus@redhat.com>

On Wed, Feb 26, 2014 at 10:45:26AM -0500, Don Zickus wrote:
> Currently if a process creates a bunch of threads using pthread_create
> and then perf is run in system_wide mode, the mmaps for those threads
> are not captured with a synthesized mmap event.
> 
> The reason is those threads are not visible when walking the /proc/
> directory looking for /proc/<pid>/maps files.  Instead they are discovered
> using the /proc/<pid>/tasks file (which the synthesized comm event uses).
> 
> This causes problems when a program is trying to map a data address to a
> tid.  Because the tid has no maps, the event is dropped.  Changing the program
> to look up using the pid instead of the tid, finds the correct maps but creates
> ugly hacks in the program to carry the correct tid around.

hm, 2 hacks comes to my mind ;-)

1) share 'struct thread::mg' among thread group (pid)

2) or lookup the thread group leader if we find out we are
   not the leader and dont have the map info (attached)

your change makes the process map info (same info) being duplicated
for all threads (eventhough it's probably not that much bytes wasted)

I think I'd prefer ad 1) ... the patch for ad 2) assumes there's
always thread group leader (which might not be the case always?)
also 'thread->pid_' handling seems troubled

I dont have code solution for 1), maybe you've already cover that
and considered it hacky.. just throwing ideas ;-)

jirka

diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
index b0f3ca8..c428186 100644
--- a/tools/perf/util/event.c
+++ b/tools/perf/util/event.c
@@ -654,9 +654,17 @@ void thread__find_addr_map(struct thread *thread,
 			   enum map_type type, u64 addr,
 			   struct addr_location *al)
 {
-	struct map_groups *mg = &thread->mg;
+	struct map_groups *mg;
 	bool load_map = false;
 
+	if (thread->tid != thread->pid_) {
+		thread = machine__findnew_thread(machine, thread->pid_, thread->pid_);
+		if (!thread)
+			return;
+	}
+
+	mg = &thread->mg;
+
 	al->machine = machine;
 	al->thread = thread;
 	al->addr = addr;

  reply	other threads:[~2014-03-05 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 15:45 [PATCH 0/2] perf: thread fixes Don Zickus
2014-02-26 15:45 ` [PATCH 1/2] perf: fix synthesizing mmaps for threads Don Zickus
2014-03-05 16:58   ` Jiri Olsa [this message]
2014-03-05 17:29     ` Don Zickus
2014-03-18  8:29   ` [tip:perf/core] perf tools: Fix " tip-bot for Don Zickus
2014-02-26 15:45 ` [PATCH 2/2] perf: Use tid in mmap/mmap2 events to find maps Don Zickus
2014-03-19 13:07   ` [tip:perf/core] perf tools: Use tid in mmap/ mmap2 " tip-bot for Don Zickus

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=20140305165857.GA28127@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@ghostprotocols.net \
    --cc=dzickus@redhat.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.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