From: Don Zickus <dzickus@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: acme@ghostprotocols.net, jolsa@redhat.com, eranian@google.com,
Don Zickus <dzickus@redhat.com>
Subject: [PATCH 2/2] perf: Use tid in mmap/mmap2 events to find maps
Date: Wed, 26 Feb 2014 10:45:27 -0500 [thread overview]
Message-ID: <1393429527-167840-3-git-send-email-dzickus@redhat.com> (raw)
In-Reply-To: <1393429527-167840-1-git-send-email-dzickus@redhat.com>
Now that we can properly synthesize threads system-wide, make sure
the mmap and mmap2 events use tids instead of pids to locate their
maps.
Signed-off-by: Don Zickus <dzickus@redhat.com>
---
tools/perf/util/machine.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
index 813e94e..eb26544 100644
--- a/tools/perf/util/machine.c
+++ b/tools/perf/util/machine.c
@@ -1026,7 +1026,7 @@ int machine__process_mmap2_event(struct machine *machine,
}
thread = machine__findnew_thread(machine, event->mmap2.pid,
- event->mmap2.pid);
+ event->mmap2.tid);
if (thread == NULL)
goto out_problem;
@@ -1074,7 +1074,7 @@ int machine__process_mmap_event(struct machine *machine, union perf_event *event
}
thread = machine__findnew_thread(machine, event->mmap.pid,
- event->mmap.pid);
+ event->mmap.tid);
if (thread == NULL)
goto out_problem;
--
1.7.11.7
next prev parent reply other threads:[~2014-02-26 15:45 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
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 ` Don Zickus [this message]
2014-03-19 13:07 ` [tip:perf/core] perf tools: Use tid in mmap/ mmap2 events to find maps 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=1393429527-167840-3-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=jolsa@redhat.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
all inboxes | Powered by JetHome®