KVM: Fix printk name error in svm.c
authorZachary Amsden <zamsden@redhat.com>
Tue, 29 Sep 2009 21:38:36 +0000 (11:38 -1000)
committerAvi Kivity <avi@redhat.com>
Thu, 3 Dec 2009 07:32:13 +0000 (09:32 +0200)
Signed-off-by: Zachary Amsden <zamsden@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
arch/x86/kvm/svm.c

index 9a4dacab6d8a9d4fb4453ae918b740ee9a4be8b7..d1036ce8917e985dea5f28d80c58e2692a5c1241 100644 (file)
@@ -330,13 +330,14 @@ static int svm_hardware_enable(void *garbage)
                return -EBUSY;
 
        if (!has_svm()) {
-               printk(KERN_ERR "svm_cpu_init: err EOPNOTSUPP on %d\n", me);
+               printk(KERN_ERR "svm_hardware_enable: err EOPNOTSUPP on %d\n",
+                      me);
                return -EINVAL;
        }
        svm_data = per_cpu(svm_data, me);
 
        if (!svm_data) {
-               printk(KERN_ERR "svm_cpu_init: svm_data is NULL on %d\n",
+               printk(KERN_ERR "svm_hardware_enable: svm_data is NULL on %d\n",
                       me);
                return -EINVAL;
        }