From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] KVM: VMX: Update instruction length on intercepted BP
Date: Tue, 16 Feb 2010 13:25:57 +0200
Message-ID: <20100216112557.GK2995@redhat.com>
References: <4B77D4DE.3030602@web.de>
 <20100214111544.GJ2511@redhat.com>
 <4B77E0E2.7030704@web.de>
 <20100214144501.GN2511@redhat.com>
 <4B7826D3.7080201@web.de>
 <20100214165319.GA19246@redhat.com>
 <4B782D97.9030304@web.de>
 <20100214172613.GB19246@redhat.com>
 <4B7837A3.4040607@web.de>
 <20100216112021.GJ2995@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>,
	kvm <kvm@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:44232 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754773Ab0BPL0A (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 16 Feb 2010 06:26:00 -0500
Content-Disposition: inline
In-Reply-To: <20100216112021.GJ2995@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tue, Feb 16, 2010 at 01:20:21PM +0200, Gleb Natapov wrote:
> On Sun, Feb 14, 2010 at 06:49:23PM +0100, Jan Kiszka wrote:
> > > Lets check if SVM works. I can do that if you tell me how.
> > 
> > - Fire up some Linux guest with gdb installed
> > - Attach gdb to gdbstub of the VM
> I get "Remote 'g' packet reply is too long". My guest and host are 64
> bit.
> 
May fault. Provided wrong file to gdb.

> > - Set a soft breakpoint in guest kernel, ideally where it does not
> >   immediately trigger, e.g. on sys_reboot (use grep sys_reboot
> >   /proc/kallsyms if you don't have symbols for the guest kernel)
> > - Start gdb /bin/true in the guest
> > - run
> > 
> > As gdb sets some automatic breakpoints, this already exercises the
> > reinjection of #BP.
> > 
> > > My concern is
> > > that if SVM doesn't work we will write another way to handle this
> > > situation that will work on SVM and VMX and then we will have code in
> > > VMX that is not needed, but we have to support it.
> > 
> > I understand your concerns, but I do not share them ATM. I bet we will
> > need some workaround for older SVM, but it will be some SVM-only thing.
> > Anyway, we can wait with this patch a few days until we know more.
> > 
> > Jan
> > 
> 
> 
> 
> --
> 			Gleb.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
			Gleb.