mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: ast@fb.com, lkml <linux-kernel@vger.kernel.org>,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	mingo@redhat.com, daniel@iogearbox.net, rostedt@goodmis.org,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	sargun@sargun.me, Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
	brendan.d.gregg@gmail.com
Subject: Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report
Date: Wed, 14 Dec 2016 22:33:21 +0530	[thread overview]
Message-ID: <77cda378-37e7-918c-05e6-09ac7b3ed5c7@linux.vnet.ibm.com> (raw)
In-Reply-To: <87k2b233up.fsf@xmission.com>



On Wednesday 14 December 2016 09:22 PM, Eric W. Biederman wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
>
>> On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
>>> I would just make the identifier a structure containing the
>>> device number and the inode number.  It didn't look like perf required
>>> the identifier to be a simple integer.
>> Right, perf doesn't care at all here, its just a transport.
> perf report?  In that case I think perf cares enough to know there is
> some identifier it is reporting things by.

Let me post v4 with this change..

Thanks
Hari

      reply	other threads:[~2016-12-14 17:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 18:19 [PATCH v3 0/3] perf: add support for analyzing events for containers Hari Bathini
2016-12-12 18:19 ` [PATCH v3 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info Hari Bathini
2016-12-12 18:27   ` Eric W. Biederman
2016-12-13 18:47     ` Hari Bathini
2016-12-13 19:58       ` Eric W. Biederman
2016-12-12 18:19 ` [PATCH v3 2/3] perf tool: " Hari Bathini
2016-12-12 21:51   ` Eric W. Biederman
2016-12-12 18:20 ` [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report Hari Bathini
2016-12-12 22:06   ` Eric W. Biederman
2016-12-13 19:07     ` Hari Bathini
2016-12-13 19:56       ` Eric W. Biederman
2016-12-14  8:24         ` Peter Zijlstra
2016-12-14 15:52           ` Eric W. Biederman
2016-12-14 17:03             ` Hari Bathini [this message]

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=77cda378-37e7-918c-05e6-09ac7b3ed5c7@linux.vnet.ibm.com \
    --to=hbathini@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=ast@fb.com \
    --cc=brendan.d.gregg@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sargun@sargun.me \
    /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®