From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH][uq/master] kvm: x86: Save/restore FPU OP, IP and DP Date: Mon, 13 Jun 2011 11:45:34 +0300 Message-ID: <4DF5CE2E.50008@redhat.com> References: <4DF33413.9070605@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm , qemu-devel , Stefan Hajnoczi , Christophe Fergeau To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:3918 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753722Ab1FMIpv (ORCPT ); Mon, 13 Jun 2011 04:45:51 -0400 In-Reply-To: <4DF33413.9070605@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 06/11/2011 12:23 PM, Jan Kiszka wrote: > From: Jan Kiszka > > These FPU states are properly maintained by KVM but not yet by TCG. So > far we unconditionally set them to 0 in the guest which may cause > state corruptions - not only during migration. > > > -#define CPU_SAVE_VERSION 12 > +#define CPU_SAVE_VERSION 13 > Incrementing the version number seems excessive - I can't imagine a real-life guest will break due to fp pointer corruption However, I don't think we have a mechanism for optional state. We discussed this during the 18th VMState Subsection Symposium and IIRC agreed to re-raise the issue when we encountered it, which appears to be now. -- error compiling committee.c: too many arguments to function