From: Eduardo Habkost Subject: [PATCH 0/3] kvm: fix cr0 initialization on SIPI reset Date: Sat, 24 Oct 2009 02:49:57 -0200 Message-ID: <1256359800-16893-1-git-send-email-ehabkost@redhat.com> Cc: kvm@vger.kernel.org To: Avi Kivity , Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28470 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751890AbZJXEuA (ORCPT ); Sat, 24 Oct 2009 00:50:00 -0400 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9O4o4Qw022821 for ; Sat, 24 Oct 2009 00:50:04 -0400 Sender: kvm-owner@vger.kernel.org List-ID: Hi, The following patches fix a bug on the SIPI reset code for SVM. cr0 was not being reset properly, making KVM keep the vcpu on paging mode, thus not being able to run the real-mode boostrap code. This bug was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=525699 The first patch is cosmetic, and it just changes the vmx code to use the same macros when initializing cr0, instead of a hardcoded hex value. The patches were tested by running a RHEL-5.4 guest and and triggering the SIPI reset by offlining and onlining cpus on the guest. They were tested on both NPT-enabled and NPT-disabled cases. -- Eduardo