From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 4/5] KVM: Lazify fpu activation and deactivation
Date: Wed, 6 Jan 2010 11:47:45 +0100
Message-ID: <20100106104744.GJ14679@amd.com>
References: <1262190342-18611-1-git-send-email-avi@redhat.com>
 <1262190342-18611-5-git-send-email-avi@redhat.com>
 <20100106002529.GA11233@amt.cnet>
 <4B4400F5.2010309@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Sheng Yang <sheng@linux.intel.com>, kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:46773 "EHLO
	TX2EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755641Ab0AFKsZ (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 6 Jan 2010 05:48:25 -0500
Content-Disposition: inline
In-Reply-To: <4B4400F5.2010309@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Jan 06, 2010 at 05:18:13AM +0200, Avi Kivity wrote:
> Joerg, what was the reason the initial npt implementation did not do
> lazy fpu switching?

The lazy fpu switching code needed cr3 accesses to be intercepted. With
NPT this was the only reason left to intercept cr3 so I decided to
switch lazy fpu switching off and don't intercept cr3 accesses.

	Joerg