From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 3/3] KVM: x86: Use FPU API Date: Mon, 17 May 2010 11:18:22 +0300 Message-ID: <4BF0FBCE.5010002@redhat.com> References: <4BEE561E.5020607@redhat.com> <1274083741-25856-1-git-send-email-sheng@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, "H. Peter Anvin" , Ingo Molnar To: Sheng Yang Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39596 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752260Ab0EQITG (ORCPT ); Mon, 17 May 2010 04:19:06 -0400 In-Reply-To: <1274083741-25856-1-git-send-email-sheng@linux.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/17/2010 11:09 AM, Sheng Yang wrote: > Convert KVM to use generic FPU API. > > Signed-off-by: Sheng Yang > --- > Like this? (Drop patch 1) > > Will be more readable with a patch that converts host_fx_image to unlazy_fpu(), and a second patch that converts guest_fx_image to the fpu API. I think unlazy_fpu() is even a performance win in case userspace doesn't do a lot of floating point (which is the case with qemu). I wonder why we didn't think of it before. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.