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: Wed, 24 Mar 2010 18:09:30 +0200 Message-ID: <4BAA393A.9000105@redhat.com> References: <20100324115900.GB14800@8bytes.org> <4BAA00B1.20407@redhat.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Ingo Molnar , Pekka Enberg , "Zhang, Yanmin" , Peter Zijlstra , Sheng Yang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti , Jes Sorensen , Gleb Natapov , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker , Gregory Haskins To: Joerg Roedel Return-path: In-Reply-To: <20100324155927.GI14800@8bytes.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 03/24/2010 05:59 PM, Joerg Roedel wrote: > > >>> I am not tied to /sys/kvm. We could also use /proc//kvm/ for >>> example. This would keep anything in the process space (except for the >>> global list of VMs which we should have anyway). >>> >>> >> How about ~/.qemu/guests/$pid? >> > That makes it hard for perf to find it and even harder to get a list of > all VMs. Looks trivial to find a guest, less so with enumerating (still doable). > With /proc//kvm/guest we could symlink all guest > directories to /proc/kvm/ and perf reads the list from there. Also perf > can easily derive the directory for a guest from its pid. > Last but not least its kernel-created and thus independent from the > userspace part being used. > Doesn't perf already has a dependency on naming conventions for finding debug information? -- error compiling committee.c: too many arguments to function