From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
 project
Date: Wed, 24 Mar 2010 20:20:10 +0200
Message-ID: <4BAA57DA.5030707@redhat.com>
References: <20100324125043.GC14800@8bytes.org> <4BAA0DFE.1080700@redhat.com> <20100324134642.GD14800@8bytes.org> <4BAA1A53.20207@redhat.com> <20100324150137.GE14800@8bytes.org> <4BAA2BF7.4060407@redhat.com> <20100324154605.GG14800@8bytes.org> <4BAA3496.2010901@redhat.com> <20100324155927.GI14800@8bytes.org> <4BAA393A.9000105@redhat.com> <20100324174703.GD3625@ghostprotocols.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Joerg Roedel <joro@8bytes.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Ingo Molnar <mingo@elte.hu>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Sheng Yang <sheng@linux.intel.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	Gleb Natapov <gleb@redhat.com>, ziteng.huang@intel.com,
	Fr?d?ric Weisbecker <fweisbec@gmail.com>,
	Gregory Haskins <ghaskins@novell.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:11374 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753119Ab0CXSUk (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 24 Mar 2010 14:20:40 -0400
In-Reply-To: <20100324174703.GD3625@ghostprotocols.net>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 03/24/2010 07:47 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 24, 2010 at 06:09:30PM +0200, Avi Kivity escreveu:
>    
>> Doesn't perf already has a dependency on naming conventions for finding
>> debug information?
>>      
> It looks at several places, from most symbol rich (/usr/lib/debug/, aka
> -debuginfo packages, where we have full symtabs) to poorest (the
> packaged binary, where we may just have a .dynsym).
>
> In an ideal world, it would just get the build-id (a SHA1 cookie that is
> in an ELF session inserted in every binary (aka DSOs), kernel module,
> kallsyms or vmlinux file) and use that to look first in a local cache
> (implemented in perf for a long time already) or in some symbol server.
>
> For instance, for a random perf.data file I collected here in my machine
> I have:
>
> [acme@doppio linux-2.6-tip]$ perf buildid-list | grep libpthread
> 5c68f7afeb33309c78037e374b0deee84dd441f6 /lib64/libpthread-2.10.2.so
> [acme@doppio linux-2.6-tip]$
>
> So I don't have to access /lib64/libpthread-2.10.2.so directly, nor some
> convention to get a debuginfo in a local file like:
>
> /usr/lib/debug/lib64/libpthread-2.10.2.so.debug
>
> Instead the tools look at:
>
> [acme@doppio linux-2.6-tip]$ l ~/.debug/.build-id/5c/68f7afeb33309c78037e374b0deee84dd441f6
> lrwxrwxrwx 1 acme acme 73 2010-01-06 18:53 /home/acme/.debug/.build-id/5c/68f7afeb33309c78037e374b0deee84dd441f6 ->  ../../lib64/libpthread-2.10.2.so/5c68f7afeb33309c78037e374b0deee84dd441f6*
>
> To find the file for that specific build-id, not the one installed in my
> machine (or on the different machine, of a different architecture) that
> may be completely unrelated, a new one, or one for a different arch.
>    

Thanks.  I believe qemu could easily act as a symbol server for this use 
case.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.