Message-ID: <555B48E6.6000307@gmail.com>
Date: Tue, 19 May 2015 08:29:58 -0600
From: David Ahern <dsahern@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
        =?UTF-8?B?TWFydGluIExpxaFr?= =?UTF-8?B?YQ==?= <mliska@suse.cz>
CC: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: introduce new two options for objdump.
References: <54CA2FB2.6070202@suse.cz> <20150519140820.GK13946@kernel.org>
In-Reply-To: <20150519140820.GK13946@kernel.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1290
Lines: 32

On 5/19/15 8:08 AM, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jan 29, 2015 at 02:03:46PM +0100, Martin Liška escreveu:
>> Newly introduced options usedfull for off-box usage:
>
>     New useful options for off-box usage:
>
>>    --objdump-prefix: specify prefix to add to the absolute paths
>>    where objdump looks for source files.
>>    --objdump-prefix-strip: indicate how many initial directory names
>>    to strip off the hardwired absolute paths, passed to objdump.
>>    It has no effect without --objdump-prefix.
>
> Does this, for instance, allows one looking at source code + assembly
> with debuginfo packages? Is that a usecase you tested this against?
>
> Anyway, sorry for the delay in processing this, fell thru the cracks ;-\
>
> Can you please respin this on top of my current perf/core, at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
>
> Thanks a lot!

Perhaps it should be generalized a bit? Right now we have symfs for the 
location of the tree for binaries. What about a srcfs for a source tree?


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