From: David Ahern <dsahern@gmail.com>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: perf and containers
Date: Fri, 30 Jun 2017 08:55:13 -0600 [thread overview]
Message-ID: <52ed4a27-498d-3f13-e9cc-236174c038c1@gmail.com> (raw)
In-Reply-To: <01937385-b6d9-d7d4-0d41-3869b1b7bb48@linux.vnet.ibm.com>
On 6/30/17 1:00 AM, Thomas-Mich Richter wrote:
> On 06/30/2017 04:16 AM, Arnaldo Carvalho de Melo wrote:
>
> [...SNIP..]
>
> I ran into a very similar issue when I tried the latest kernel 4.12 perf name space support.
> I was able to find the new PERF_RECORD_NAMESPACE entries in the perf.data file
> but do not know how to interpret the ino-numbers shown in those entries.
> Right now the wrong symbols will be displayed...
>
> How to interpret the inode numbers the perf NAMESPACE event emits?
The device and inode number can be used as an identifier (e.g., combine
into a u64) for the namespace when processing events.
next prev parent reply other threads:[~2017-06-30 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 20:33 perf and containers Brendan Gregg
2017-06-30 2:16 ` Arnaldo Carvalho de Melo
2017-06-30 7:00 ` Thomas-Mich Richter
2017-06-30 14:55 ` David Ahern [this message]
2017-06-30 17:13 ` Milian Wolff
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=52ed4a27-498d-3f13-e9cc-236174c038c1@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=tmricht@linux.vnet.ibm.com \
/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).