From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: perf software events broken in containers Date: Thu, 23 Mar 2017 08:21:27 -0600 Message-ID: References: <8c4186d0-bfbf-6f1a-c953-9859bf057856@redhat.com> <4bf76843-d25e-4cda-30ce-0984f8778704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-pf0-f172.google.com ([209.85.192.172]:34690 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752595AbdCWOVa (ORCPT ); Thu, 23 Mar 2017 10:21:30 -0400 Received: by mail-pf0-f172.google.com with SMTP id p189so83284208pfp.1 for ; Thu, 23 Mar 2017 07:21:29 -0700 (PDT) In-Reply-To: Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Brendan Gregg , William Cohen Cc: "linux-perf-use." 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.