From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M0LVF-0000jI-Dw
	for qemu-devel@nongnu.org; Sat, 02 May 2009 16:08:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M0LVB-0000fO-P4
	for qemu-devel@nongnu.org; Sat, 02 May 2009 16:08:05 -0400
Received: from [199.232.76.173] (port=45139 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M0LVB-0000fG-MD
	for qemu-devel@nongnu.org; Sat, 02 May 2009 16:08:01 -0400
Received: from mx2.redhat.com ([66.187.237.31]:56786)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1M0LVB-0006yz-6S
	for qemu-devel@nongnu.org; Sat, 02 May 2009 16:08:01 -0400
Date: Sat, 2 May 2009 23:07:54 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH  0/8] kvm: Fixes, cleanups and live
	migration
Message-ID: <20090502200754.GB13933@redhat.com>
References: <20090501211717.24514.23246.stgit@mchn012c.ww002.siemens.net>
	<49FB7A40.1020005@us.ibm.com> <20090502074041.GB7198@redhat.com>
	<49FC4F90.1030901@codemonkey.ws>
	<20090502172308.GA13933@redhat.com> <49FC9B39.4080408@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49FC9B39.4080408@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org

On Sat, May 02, 2009 at 10:12:57PM +0300, Avi Kivity wrote:
> Gleb Natapov wrote:
>>>
>>> I think the right thing to do with this is introduce a kvm-cpu savevm 
>>>  that stores this information since it isn't relevant to TCG.  I 
>>> think  it's arguable whether you want instruction length there (can 
>>> you get it  reliably on SVM?).
>>>
>>>     
>> We can't get it on SVM without instruction decoding, but it is not required
>> on SVM. It is absolutely essential for soft interrupt/exception injection
>> on VMX and has to be a part of migratable state.
>>   
>
> We need it in some neutral form so cross-vendor migration can work.
>
VMX->SVM No problem.
SVM->VMX bad luck :)  We will have to decode instruction ourself. 

--
			Gleb.