From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756125Ab0CVUcg (ORCPT ); Mon, 22 Mar 2010 16:32:36 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:47231 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754820Ab0CVUce (ORCPT ); Mon, 22 Mar 2010 16:32:34 -0400 Date: Mon, 22 Mar 2010 21:32:15 +0100 From: Ingo Molnar To: Anthony Liguori Cc: Avi Kivity , 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 Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project Message-ID: <20100322203215.GB18126@elte.hu> 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> <4BA7C4FF.3080407@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BA7C4FF.3080407@codemonkey.ws> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Anthony Liguori wrote: > On 03/22/2010 02:22 PM, Ingo Molnar wrote: > >>Transitive had a product that was using a KVM context to run their > >>binary translator which allowed them full access to the host > >>processes virtual address space range. In this case, there is no > >>kernel and there are no devices. > > > > And your point is that such vcpus should be excluded from profiling just > > because they fall outside the Qemu/libvirt umbrella? > > You don't instrument it the way you'd instrument an operating system so no, > you don't want it to show up in perf kvm top. Erm, why not? It's executing a virtualized CPU, so sure it makes sense to allow the profiling of it! It might even not be the weird case you mentioned by some competing virtualization project to Qemu ... So your argument is wrong on several technical levels, sorry. Thanks, Ingo