linux-kernel - Re: [RFC PATCH] perf: Container-aware tracing support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 17 Jul 2015 14:26:17 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Aravinda Prasad <aravinda@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, rostedt@...dmis.org,
	mingo@...hat.com, paulus@...ba.org, acme@...nel.org,
	hbathini@...ux.vnet.ibm.com, ananth@...ibm.com
Subject: Re: [RFC PATCH] perf: Container-aware tracing support


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Wed, Jul 15, 2015 at 02:38:36PM +0530, Aravinda Prasad wrote:
> > Current tracing infrastructure such as perf and ftrace reports system
> > wide data when invoked inside a container. It is required to restrict
> > events specific to a container context when such tools are invoked
> > inside a container.
> > 
> > This RFC patch supports filtering container specific events, without
> > any change in the user interface, when invoked within a container for
> > the perf utility; such support needs to be extended to ftrace. This
> > patch assumes that the debugfs is available within the container and
> > all the processes running inside a container are grouped into a single
> > perf_event subsystem of cgroups. This patch piggybacks on the existing
> > support available for tracing with cgroups [1] by setting the cgrp
> > member of the event structure to the cgroup of the context perf tool
> > is invoked from.
> > 
> > However, this patch is not complete and requires more work to fully
> > support tracing inside a container. This patch is intended to initiate
> > the discussion on having container-aware tracing support. A detailed
> > explanation on what is supported and pending issues are mentioned
> > below.
> 
> tracing is outside the scope of perf; I suspect you want tracefs to be
> sensitive to filesystem namespaces and all that that entails.

I'd correct that to:

  > ftrace is outside the scope of perf; I suspect you want tracefs to be 
  > sensitive to filesystem namespaces and all that that entails.

because perf very much does tracing as well, we have 'perf trace' for example, and 
obviously the whole ring-buffer is a trace buffer and perf.data is a trace dump of 
that.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/