提交 1f5b77f5 编写于 作者: B Borislav Petkov 提交者: Avi Kivity

KVM: SVM: Cleanup error statements

Use __func__ instead of the function name in svm_hardware_enable since
those things tend to get out of sync. This also slims down printk line
length in conjunction with using pr_err.

No functionality change.

Cc: Joerg Roedel <joro@8bytes.org>
Cc: Avi Kivity <avi@redhat.com>
Signed-off-by: NBorislav Petkov <bp@alien8.de>
Signed-off-by: NAvi Kivity <avi@redhat.com>
上级 bf4ca23e
...@@ -630,15 +630,12 @@ static int svm_hardware_enable(void *garbage) ...@@ -630,15 +630,12 @@ static int svm_hardware_enable(void *garbage)
return -EBUSY; return -EBUSY;
if (!has_svm()) { if (!has_svm()) {
printk(KERN_ERR "svm_hardware_enable: err EOPNOTSUPP on %d\n", pr_err("%s: err EOPNOTSUPP on %d\n", __func__, me);
me);
return -EINVAL; return -EINVAL;
} }
sd = per_cpu(svm_data, me); sd = per_cpu(svm_data, me);
if (!sd) { if (!sd) {
printk(KERN_ERR "svm_hardware_enable: svm_data is NULL on %d\n", pr_err("%s: svm_data is NULL on %d\n", __func__, me);
me);
return -EINVAL; return -EINVAL;
} }
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册