From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54825) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhyT9-0005lv-MB for qemu-devel@nongnu.org; Tue, 24 Jul 2018 10:39:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhyT7-0006Xy-1b for qemu-devel@nongnu.org; Tue, 24 Jul 2018 10:39:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36534) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fhyT6-0006Xf-RC for qemu-devel@nongnu.org; Tue, 24 Jul 2018 10:39:16 -0400 Date: Tue, 24 Jul 2018 11:39:14 -0300 From: Eduardo Habkost Message-ID: <20180724143914.GE3896@localhost.localdomain> References: <1519726932-13833-1-git-send-email-liran.alon@oracle.com> <20180724112911.GA2314@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180724112911.GA2314@work-vm> Subject: Re: [Qemu-devel] [PATCH] KVM: x86: Add support for save/load MSR_SMI_COUNT List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: Liran Alon , qemu-devel@nongnu.org, pbonzini@redhat.com, mtosatti@redhat.com, rth@twiddle.net, kvm@vger.kernel.org, Konrad Rzeszutek Wilk , quintela@redhat.com On Tue, Jul 24, 2018 at 12:29:12PM +0100, Dr. David Alan Gilbert wrote: > * Liran Alon (liran.alon@oracle.com) wrote: > > This MSR returns the number of #SMIs that occurred on > > CPU since boot. > > > > KVM commit 52797bf9a875 ("KVM: x86: Add emulation of MSR_SMI_COUNT") > > introduced support for emulating this MSR. > > > > This commit adds support for QEMU to save/load this > > MSR for migration purposes. > > > > Signed-off-by: Liran Alon > > Reviewed-by: Konrad Rzeszutek Wilk > > Signed-off-by: Konrad Rzeszutek Wilk > > Note this breaks 2.12->2.11 migration if SMM is enabled > with a: > > qemu-system-x86_64: error while loading state for instance 0x0 of device 'cpu' Right, the MSR can't be enabled unconditionally. It looks like there's no CPUID bit for reporting the MSR as available? How exactly would guests know if the MSR is really safe to use? -- Eduardo