From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751667AbcERDEp (ORCPT ); Tue, 17 May 2016 23:04:45 -0400 Received: from mail-io0-f196.google.com ([209.85.223.196]:36129 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751180AbcERDEn (ORCPT ); Tue, 17 May 2016 23:04:43 -0400 Subject: Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs To: Hekuang , peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, jolsa@redhat.com, wangnan0@huawei.com, jpoimboe@redhat.com, ak@linux.intel.com, eranian@google.com, namhyung@kernel.org, adrian.hunter@intel.com, sukadev@linux.vnet.ibm.com, masami.hiramatsu.pt@hitachi.com, tumanova@linux.vnet.ibm.com, kan.liang@intel.com, penberg@kernel.org References: <20160513180104.GL11346@kernel.org> <1463213965-35230-1-git-send-email-hekuang@huawei.com> <4572f136-796d-059f-6b81-613e8f63be24@gmail.com> <573922AE.5030002@huawei.com> <573BC99E.4020004@huawei.com> <1193b9ba-7037-22c6-a54a-6992e155be46@gmail.com> <573BD810.8030104@huawei.com> Cc: linux-kernel@vger.kernel.org From: David Ahern Message-ID: <7a36f7bc-0d16-4748-63a7-c33f6b129b5a@gmail.com> Date: Tue, 17 May 2016 21:04:38 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <573BD810.8030104@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/17/16 8:48 PM, Hekuang wrote: >> I don't understand why dso-prefix option is needed? Why make me type >> yet more options to the analysis command? Why can't the directory be >> located under the symfs tree in a known location and populated the >> same way it is without symfs? >> >> > Because the default buidid folder path is $HOME/.debug/.buildid, > and this $HOME is on the target machine, not the same as $HOME > on the host. Without that option, we need to copy $HOME/.debug/.buildid > to the 'known location in symfs', that's also an extra work. > My argument for symfs is that $HOME is not relevant or if it is the path is symfs/$HOME. The use case is dealing with countless images -- some development, some production. I should be able to nuke the symfs when the analysis is done and everything related to it is gone. With the $HOME/.debug path it just grows on and on with no real means of pruning it. If the vdsos are for a particular symfs then why aren't the vdso's under it in a known location?