From: Jeff Dike <jdike@addtoit.com>
To: Avi Kivity <avi@qumranet.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
KVM devel <kvm-devel@lists.sourceforge.net>
Subject: [PATCH 1/3] KVM - Add missing kvm_run initializations
Date: Mon, 16 Jul 2007 15:24:46 -0400 [thread overview]
Message-ID: <20070716192446.GA16243@c2.user-mode-linux.org> (raw)
There are a bunch of missing initializations of run->exit_reason and
associated data.
kvm_hypercall wasn't setting exit_reason at all.
When exit_reason is KVM_EXIT_MMIO, the mmio data isn't initialized. I
don't know what it should be, so I just stuck a FIXME in there.
There were some missing initializations of hardware_exit_reason with
KVM_EXIT_UNKNOWN, so I added those. One case had exit_reason = 0,
which I changed to KVM_EXIT_UNKNOWN.
I did a pass over all of the return 0 paths in the exit handler
callbacks, so this should cover everything.
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
--
drivers/kvm/kvm_main.c | 3 +++
drivers/kvm/svm.c | 3 +++
drivers/kvm/vmx.c | 4 +++-
3 files changed, 9 insertions(+), 1 deletion(-)
Index: kvm/drivers/kvm/kvm_main.c
===================================================================
--- kvm.orig/drivers/kvm/kvm_main.c
+++ kvm/drivers/kvm/kvm_main.c
@@ -1370,6 +1370,7 @@ int kvm_hypercall(struct kvm_vcpu *vcpu,
run->hypercall.ret = ret;
run->hypercall.longmode = is_long_mode(vcpu);
kvm_arch_ops->decache_regs(vcpu);
+ run->exit_reason = KVM_EXIT_HYPERCALL;
return 0;
}
vcpu->regs[VCPU_REGS_RAX] = ret;
@@ -1928,6 +1929,8 @@ static int kvm_vcpu_ioctl_run(struct kvm
if (r == EMULATE_DO_MMIO) {
/*
* Read-modify-write. Back to userspace.
+ *
+ * FIXME - kvm_run->mmio not initialized
*/
kvm_run->exit_reason = KVM_EXIT_MMIO;
r = 0;
Index: kvm/drivers/kvm/svm.c
===================================================================
--- kvm.orig/drivers/kvm/svm.c
+++ kvm/drivers/kvm/svm.c
@@ -929,6 +929,7 @@ static int pf_interception(struct kvm_vc
return 1;
case EMULATE_DO_MMIO:
++vcpu->stat.mmio_exits;
+ /* FIXME - kvm_run->mmio not initialized */
kvm_run->exit_reason = KVM_EXIT_MMIO;
return 0;
case EMULATE_FAIL:
@@ -938,6 +939,7 @@ static int pf_interception(struct kvm_vc
BUG();
}
+ kvm_run->hw.hardware_exit_reason = vcpu->svm->vmcb->control.exit_code;
kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
return 0;
}
@@ -1135,6 +1137,7 @@ static int invalid_op_interception(struc
static int task_switch_interception(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
{
printk(KERN_DEBUG "%s: task swiche is unsupported\n", __FUNCTION__);
+ kvm_run->hw.hardware_exit_reason = vcpu->svm->vmcb->control.exit_code;
kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
return 0;
}
Index: kvm/drivers/kvm/vmx.c
===================================================================
--- kvm.orig/drivers/kvm/vmx.c
+++ kvm/drivers/kvm/vmx.c
@@ -1610,6 +1610,7 @@ static int handle_exception(struct kvm_v
return 1;
case EMULATE_DO_MMIO:
++vcpu->stat.mmio_exits;
+ /* FIXME - kvm_run->mmio not initialized */
kvm_run->exit_reason = KVM_EXIT_MMIO;
return 0;
case EMULATE_FAIL:
@@ -1807,7 +1808,8 @@ static int handle_cr(struct kvm_vcpu *vc
default:
break;
}
- kvm_run->exit_reason = 0;
+ kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
+ kvm_run->hw.hardware_exit_reason = vmcs_read32(VM_EXIT_REASON);
printk(KERN_ERR "kvm: unhandled control register: op %d cr %d\n",
(int)(exit_qualification >> 4) & 3, cr);
return 0;
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike-OPE4K8JWMJJBDgjK7y7TUQ@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: KVM devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH 1/3] KVM - Add missing kvm_run initializations
Date: Mon, 16 Jul 2007 15:24:46 -0400 [thread overview]
Message-ID: <20070716192446.GA16243@c2.user-mode-linux.org> (raw)
There are a bunch of missing initializations of run->exit_reason and
associated data.
kvm_hypercall wasn't setting exit_reason at all.
When exit_reason is KVM_EXIT_MMIO, the mmio data isn't initialized. I
don't know what it should be, so I just stuck a FIXME in there.
There were some missing initializations of hardware_exit_reason with
KVM_EXIT_UNKNOWN, so I added those. One case had exit_reason = 0,
which I changed to KVM_EXIT_UNKNOWN.
I did a pass over all of the return 0 paths in the exit handler
callbacks, so this should cover everything.
Signed-off-by: Jeff Dike <jdike-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
--
drivers/kvm/kvm_main.c | 3 +++
drivers/kvm/svm.c | 3 +++
drivers/kvm/vmx.c | 4 +++-
3 files changed, 9 insertions(+), 1 deletion(-)
Index: kvm/drivers/kvm/kvm_main.c
===================================================================
--- kvm.orig/drivers/kvm/kvm_main.c
+++ kvm/drivers/kvm/kvm_main.c
@@ -1370,6 +1370,7 @@ int kvm_hypercall(struct kvm_vcpu *vcpu,
run->hypercall.ret = ret;
run->hypercall.longmode = is_long_mode(vcpu);
kvm_arch_ops->decache_regs(vcpu);
+ run->exit_reason = KVM_EXIT_HYPERCALL;
return 0;
}
vcpu->regs[VCPU_REGS_RAX] = ret;
@@ -1928,6 +1929,8 @@ static int kvm_vcpu_ioctl_run(struct kvm
if (r == EMULATE_DO_MMIO) {
/*
* Read-modify-write. Back to userspace.
+ *
+ * FIXME - kvm_run->mmio not initialized
*/
kvm_run->exit_reason = KVM_EXIT_MMIO;
r = 0;
Index: kvm/drivers/kvm/svm.c
===================================================================
--- kvm.orig/drivers/kvm/svm.c
+++ kvm/drivers/kvm/svm.c
@@ -929,6 +929,7 @@ static int pf_interception(struct kvm_vc
return 1;
case EMULATE_DO_MMIO:
++vcpu->stat.mmio_exits;
+ /* FIXME - kvm_run->mmio not initialized */
kvm_run->exit_reason = KVM_EXIT_MMIO;
return 0;
case EMULATE_FAIL:
@@ -938,6 +939,7 @@ static int pf_interception(struct kvm_vc
BUG();
}
+ kvm_run->hw.hardware_exit_reason = vcpu->svm->vmcb->control.exit_code;
kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
return 0;
}
@@ -1135,6 +1137,7 @@ static int invalid_op_interception(struc
static int task_switch_interception(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
{
printk(KERN_DEBUG "%s: task swiche is unsupported\n", __FUNCTION__);
+ kvm_run->hw.hardware_exit_reason = vcpu->svm->vmcb->control.exit_code;
kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
return 0;
}
Index: kvm/drivers/kvm/vmx.c
===================================================================
--- kvm.orig/drivers/kvm/vmx.c
+++ kvm/drivers/kvm/vmx.c
@@ -1610,6 +1610,7 @@ static int handle_exception(struct kvm_v
return 1;
case EMULATE_DO_MMIO:
++vcpu->stat.mmio_exits;
+ /* FIXME - kvm_run->mmio not initialized */
kvm_run->exit_reason = KVM_EXIT_MMIO;
return 0;
case EMULATE_FAIL:
@@ -1807,7 +1808,8 @@ static int handle_cr(struct kvm_vcpu *vc
default:
break;
}
- kvm_run->exit_reason = 0;
+ kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
+ kvm_run->hw.hardware_exit_reason = vmcs_read32(VM_EXIT_REASON);
printk(KERN_ERR "kvm: unhandled control register: op %d cr %d\n",
(int)(exit_qualification >> 4) & 3, cr);
return 0;
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next reply other threads:[~2007-07-16 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 19:24 Jeff Dike [this message]
2007-07-16 19:24 ` [PATCH 1/3] KVM - Add missing kvm_run initializations Jeff Dike
2007-07-17 8:12 ` Avi Kivity
2007-07-17 8:12 ` Avi Kivity
2007-07-17 16:26 ` Jeff Dike
2007-07-18 10:39 ` Avi Kivity
2007-07-18 10:39 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070716192446.GA16243@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.