From: Jerone Young <jyoung5@us.ibm.com>
To: kvm@vger.kernel.org
Subject: [PATCH] Fix breakpoints coming into KVM that are corrupted from qemu
Date: Thu, 22 May 2008 16:33:23 -0500 [thread overview]
Message-ID: <f5749628781bdb9e6bde.1211492003@thinkpadL> (raw)
1 file changed, 2 insertions(+)
qemu/qemu-kvm.c | 2 ++
Bad breakpoints are being passed down to KVM due to the fact that breakpoint structure in the kvm_debug_guest structure are not being initialized. This fixes this.
This fix can also be found in the RFC patches that Jan Kiszka has sent for adding soft breakpoints.
Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -704,6 +704,8 @@ int kvm_update_debugger(CPUState *env)
struct kvm_debug_guest dbg;
int i;
+ memset(dbg.breakpoints, 0, sizeof(dbg.breakpoints));
+
dbg.enabled = 0;
if (env->nb_breakpoints || env->singlestep_enabled) {
dbg.enabled = 1;
next reply other threads:[~2008-05-22 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 21:33 Jerone Young [this message]
2008-05-25 10:55 ` [PATCH] Fix breakpoints coming into KVM that are corrupted from qemu 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=f5749628781bdb9e6bde.1211492003@thinkpadL \
--to=jyoung5@us.ibm.com \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox