>From 554315592b05eabf0355ac63145c28e11358af1f Mon Sep 17 00:00:00 2001
From: Amit Shah <[EMAIL PROTECTED]>
Date: Sun, 18 Nov 2007 00:03:27 +0530
Subject: [PATCH] KVM: Use write_emulated and not write_std, which is not
implemented
... and calling write_emulated should work just as well
in place of write_std.
Signed-off-by: Amit Shah <[EMAIL PROTECTED]>
---
drivers/kvm/x86_emulate.c | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index 2765559..c2c9c8a 100644
--- a/drivers/kvm/x86_emulate.c
+++ b/drivers/kvm/x86_emulate.c
@@ -1076,9 +1076,10 @@ static inline int emulate_grp45(struct x86_emulate_ctxt
*ctxt,
}
register_address_increment(c->regs[VCPU_REGS_RSP],
-c->dst.bytes);
- rc = ops->write_std(register_address(ctxt->ss_base,
- c->regs[VCPU_REGS_RSP]), &c->dst.val,
- c->dst.bytes, ctxt->vcpu);
+ rc = ops->write_emulated(register_address(ctxt->ss_base,
+ c->regs[VCPU_REGS_RSP]),
+ &c->dst.val,
+ c->dst.bytes, ctxt->vcpu);
if (rc != 0)
return rc;
c->dst.type = OP_NONE;
--
1.4.4.2
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
