From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project Date: Mon, 22 Mar 2010 22:45:16 +0200 Message-ID: <4BA7D6DC.7060601@redhat.com> References: <20100322143212.GE14201@elte.hu> <4BA7821C.7090900@codemonkey.ws> <20100322155505.GA18796@elte.hu> <4BA796DF.7090005@redhat.com> <20100322165107.GD18796@elte.hu> <4BA7A406.9050203@redhat.com> <20100322173400.GB15795@elte.hu> <4BA7B87A.8060104@codemonkey.ws> <20100322192259.GD21919@elte.hu> <4BA7C8C6.7080604@redhat.com> <20100322203518.GC18126@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Pekka Enberg , "Zhang, Yanmin" , Peter Zijlstra , Sheng Yang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti , oerg Roedel , Jes Sorensen , Gleb Natapov , Zachary Amsden , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker , Gregory Haskins To: Ingo Molnar Return-path: In-Reply-To: <20100322203518.GC18126@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 03/22/2010 10:35 PM, Ingo Molnar wrote: > >>> And your point is that such vcpus should be excluded from profiling just >>> because they fall outside the Qemu/libvirt umbrella? >>> >>> That is a ridiculous position. >>> >>> >> Non-guest vcpus will not be able to provide Linux-style symbols. >> > And why do you say that it makes no sense to profile them? > It makes sense to profile them, but you don't need to contact their userspace tool for that. > Also, why do you define 'guest vcpus' to be 'Qemu started guest vcpus'? If > some other KVM using project (which you encouraged just a few mails ago) > starts a vcpu we still want to be able to profile them. > > Maybe it should provide a mechanism for libvirt to list it. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.