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 10:59:05 +0200 Message-ID: <4BA9D459.6070502@redhat.com> References: <20100322173400.GB15795@elte.hu> <4BA7B9E0.5080009@codemonkey.ws> <20100322192739.GE21919@elte.hu> <4BA7C96D.2020702@redhat.com> <4BA7E9D9.5060800@codemonkey.ws> <20100323140608.GJ1940@8bytes.org> <4BA8EEDE.8070309@redhat.com> <20100323182153.GA14800@8bytes.org> <87hbo6fgpy.fsf@basil.nowhere.org> <4BA9B454.5090908@redhat.com> <20100324073854.GD20695@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Joerg Roedel , 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 , Zachary Amsden , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker , Gregory Haskins To: Andi Kleen Return-path: In-Reply-To: <20100324073854.GD20695@one.firstfloor.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 03/24/2010 09:38 AM, Andi Kleen wrote: >> If you're profiling a single guest it makes more sense to do this from >> inside the guest - you can profile userspace as well as the kernel. >> > I'm interested in debugging the guest without guest cooperation. > > In many cases qemu's new gdb stub works for that, but in some cases > I would prefer instruction/branch traces over standard gdb style > debugging. > Isn't gdb supposed to be able to use branch traces? It makes sense to expose them via the gdb stub then. Not to say an external tool doesn't make sense. -- error compiling committee.c: too many arguments to function