From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: Nested SVM and migration Date: Wed, 24 Feb 2010 16:23:26 +0100 Message-ID: <20100224152325.GA3168@amd.com> References: <4B80347E.7000003@redhat.com> <20100220201822.GG20833@8bytes.org> <4B806FB9.20009@redhat.com> <20100221121008.GI20833@8bytes.org> <4B8125E2.8050309@redhat.com> <20100221124141.GA26465@8bytes.org> <4B812CE9.2070107@redhat.com> <20100221130915.GB26465@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Avi Kivity , Zachary Amsden , kvm To: Joerg Roedel Return-path: Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:36446 "EHLO TX2EHSOBE004.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756256Ab0BXPXk (ORCPT ); Wed, 24 Feb 2010 10:23:40 -0500 Content-Disposition: inline In-Reply-To: <20100221130915.GB26465@8bytes.org> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Feb 21, 2010 at 02:09:15PM +0100, Joerg Roedel wrote: > On Sun, Feb 21, 2010 at 02:54:01PM +0200, Avi Kivity wrote: > > So, if some other cpu (or the guest itself, with appropriate > > permissions) modifies the msr permission bitmap, svm will not notice > > this? svm loads the bitmap during entry? > > Yes. Talked again with a few people about it and the architectural answer is a bit different. The right answer to that is: The cpu is allowed to load the msr permission map to internal state, but not required to do it by the architecture. The result of changing the msr permission map of a running vmcb is undefined. So we are fine with the way nested svm does it. And we don't need to care about that situation at all and just migrate whats in guest memory. Thanks, Joerg