From: David Ahern <dsahern@gmail.com>
To: Brendan Gregg <brendan.d.gregg@gmail.com>,
William Cohen <wcohen@redhat.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: perf software events broken in containers
Date: Thu, 23 Mar 2017 08:21:27 -0600 [thread overview]
Message-ID: <f95c7553-51f1-cee9-b8cc-643c32b0f72c@gmail.com> (raw)
In-Reply-To: <CAE40pdcbbU=e6YXTivOW1=w2urucbQknUZc9VzebPgHeiLrKqw@mail.gmail.com>
On 3/22/17 3:35 PM, Brendan Gregg wrote:
> We also found that docker explicitly blocks perf_event_open() by default[1]:
>
> "perf_event_open Tracing/profiling syscall, which could leak a lot
> of information on the host."
as it should. The event collection does not discriminate by namespaces.
next prev parent reply other threads:[~2017-03-23 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 18:24 perf software events broken in containers Brendan Gregg
2017-03-22 19:15 ` William Cohen
2017-03-22 19:59 ` Brendan Gregg
2017-03-22 20:29 ` William Cohen
2017-03-22 21:35 ` Brendan Gregg
2017-03-23 14:21 ` David Ahern [this message]
2017-03-27 16:10 ` Frank Ch. Eigler
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=f95c7553-51f1-cee9-b8cc-643c32b0f72c@gmail.com \
--to=dsahern@gmail.com \
--cc=brendan.d.gregg@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=wcohen@redhat.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).