Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752468AbdGGTgp (ORCPT <rfc822;w@1wt.eu>);
        Fri, 7 Jul 2017 15:36:45 -0400
Received: from sub5.mail.dreamhost.com ([208.113.200.129]:34579 "EHLO
        homiemail-a83.g.dreamhost.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1750848AbdGGTgo (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 7 Jul 2017 15:36:44 -0400
Date: Fri, 7 Jul 2017 12:36:41 -0700
From: Krister Johansen <kjlx@templeofstupid.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Krister Johansen <kjlx@templeofstupid.com>,
        Brendan Gregg <brendan.d.gregg@gmail.com>,
        Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        linux-kernel@vger.kernel.org,
        Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 tip/perf/core 1/6] perf symbols: find symbols in
 different mount namespace
Message-ID: <20170707193640.GA2554@templeofstupid.com>
References: <20170705204511.GD29683@templeofstupid.com>
 <1499305693-1599-1-git-send-email-kjlx@templeofstupid.com>
 <1499305693-1599-2-git-send-email-kjlx@templeofstupid.com>
 <20170706194130.GM27350@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170706194130.GM27350@kernel.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 966
Lines: 18

On Thu, Jul 06, 2017 at 04:41:30PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jul 05, 2017 at 06:48:08PM -0700, Krister Johansen escreveu:
> > Teach perf how to resolve symbols from binaries that are in a different
> > mount namespace from the tool.  This allows perf to generate meaningful
> > stack traces even if the binary resides in a different mount namespace
> > from the tool.
> 
> I was trying to find a way to test after applying each of the patches in
> this series, when it ocurred to me that if a process that appears on a
> perf.data file has exit, how can we access /proc/%ITS_PID/something?

You're correct.  We can't access /proc/<PID>/whatever once the process
has exited.  That was the impeteus for patches 4 and 6, which allow us
to capture the binary (and debuginfo, if it exists) into the buildid
cache so that if we do have a trace that exists after a process or
container exists, we'll still be able to resolve some of the symbols.

-K