Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=217648638ccb62dfeea5ac5fe768539cdee61ed0
Commit:     217648638ccb62dfeea5ac5fe768539cdee61ed0
Parent:     12b7d28fc102b772eb70f98491587ec5ee717baf
Author:     Ryan Harper <[EMAIL PROTECTED]>
AuthorDate: Tue Sep 18 14:05:16 2007 -0500
Committer:  Avi Kivity <[EMAIL PROTECTED]>
CommitDate: Wed Jan 30 17:52:48 2008 +0200

    KVM: MMU: Ignore reserved bits in cr3 in non-pae mode
    
    This patch removes the fault injected when the guest attempts to set 
reserved
    bits in cr3.  X86 hardware doesn't generate a fault when setting reserved 
bits.
    The result of this patch is that vmware-server, running within a kvm guest,
    boots and runs memtest from an iso.
    
    Signed-off-by: Ryan Harper <[EMAIL PROTECTED]>
    Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
 drivers/kvm/kvm_main.c |   11 ++++-------
 1 files changed, 4 insertions(+), 7 deletions(-)

diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 82cc7ae..2d55bab 100644
--- a/drivers/kvm/kvm_main.c
+++ b/drivers/kvm/kvm_main.c
@@ -554,14 +554,11 @@ void set_cr3(struct kvm_vcpu *vcpu, unsigned long cr3)
                                inject_gp(vcpu);
                                return;
                        }
-               } else {
-                       if (cr3 & CR3_NONPAE_RESERVED_BITS) {
-                               printk(KERN_DEBUG
-                                      "set_cr3: #GP, reserved bits\n");
-                               inject_gp(vcpu);
-                               return;
-                       }
                }
+               /*
+                * We don't check reserved bits in nonpae mode, because
+                * this isn't enforced, and VMware depends on this.
+                */
        }
 
        mutex_lock(&vcpu->kvm->lock);
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to