All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: jyoung5@us.ibm.com
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [kvm-userspace] new functions on_vcpu() causing segafault when trying to use breakpoints
Date: Fri, 30 May 2008 22:23:12 +0200	[thread overview]
Message-ID: <48406230.5040300@web.de> (raw)
In-Reply-To: <1212175668.24409.9.camel@thinkpadL>

[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]

Jerone Young wrote:
> New code recently added to the repository has made some modifications to
> the kvm_update_debugger() function in qemu-kvm.c. Where as no longer  to
> just call kvm_guest_debug...Now there is a new fuction on_vcpu() that
> places things in work queues and launches them.
> 
> The problem is when kvm_invold_guest_debug() gets called, it segfaults
> calling kvm_guest_debug().

I bet this piece from [1] will solve it:

Index: b/qemu/qemu-kvm.c
===================================================================
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -268,7 +268,7 @@ static void kvm_main_loop_wait(CPUState 
 	exit(1);
     }
 
-
+    cpu_single_env = env;
     flush_queued_work(env);
 
     if (vcpu_info[env->cpu_index].stop) {


I didn't bother posting it separately as I (obviously wrongly) assumed
this wouldn't trigger for the existing code.

> 
> What exactly is the point of complicating this? 

The old code quickly live-locked when you invoked kvm_guest_debug while
the target vcpu was still running. I suggested to stop the vcpu when
invoking this (and other problematic) services, Avi preferred the
on_vcpu aproach. And that, indeed, turned out to be cleaner and easier
reusable.

> 
> This code does segfault on x86 also. For now I have just placed the old
> code back locally.

I would be happy if you could give my patches a spin as well. I was
using them for kernel debugging during this week, but I guess I'm still
alone. :->

Jan

[1] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/17968


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2008-05-30 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 19:27 [kvm-userspace] new functions on_vcpu() causing segafault when trying to use breakpoints Jerone Young
2008-05-30 20:23 ` Jan Kiszka [this message]
2008-05-30 20:55   ` Jerone Young

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=48406230.5040300@web.de \
    --to=jan.kiszka@web.de \
    --cc=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 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.