All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm-qemu: Proper vm_stop on debug events
Date: Thu, 22 May 2008 19:35:32 -0500	[thread overview]
Message-ID: <48361154.4080805@codemonkey.ws> (raw)
In-Reply-To: <48360B4B.10105@web.de>

Jan Kiszka wrote:
> When a vcpu exits after hitting a debug exception, we have to invoke
> vm_stop(EXCP_DEBUG). But this has to take place over the io-thread.
>
> This patch introduces kvm_debug_stop_requested to signal this event, and
> it takes care that the interrupted vcpu itself goes immediately into
> stop state.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
> ---
>  qemu/qemu-kvm.c |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
>
> Index: b/qemu/qemu-kvm.c
> ===================================================================
> --- a/qemu/qemu-kvm.c
> +++ b/qemu/qemu-kvm.c
> @@ -58,6 +58,8 @@ pthread_t io_thread;
>  static int io_thread_fd = -1;
>  static int io_thread_sigfd = -1;
>  
> +static int kvm_debug_stop_requested;
> +
>   

Why use this instead of just keying off of exception_index == EXCP_DEBUG?

>  static inline unsigned long kvm_get_thread_id(void)
>  {
>      return syscall(SYS_gettid);
> @@ -517,6 +519,10 @@ int kvm_main_loop(void)
>              qemu_system_powerdown();
>          else if (qemu_reset_requested())
>  	    qemu_kvm_system_reset();
> +	else if (kvm_debug_stop_requested) {
> +	    kvm_debug_stop_requested = 0;
> +	    vm_stop(EXCP_DEBUG);
> +	}
>      }
>  
>      pause_all_threads();
> @@ -529,7 +535,8 @@ static int kvm_debug(void *opaque, int v
>  {
>      CPUState *env = cpu_single_env;
>  
> -    env->exception_index = EXCP_DEBUG;
> +    kvm_debug_stop_requested = 1;
> +    vcpu_info[vcpu].stopped = 1;
>   

This isn't quite right.  In the very least, you need to set stopping = 0 
and signal on the qemu_pause_cond.  Thinking it through more though, a 
breakpoint should stop all VCPUs, right?

vm_stop(EXCP_DEBUG) will actually do this.  It invokes the 
vm_state_notify callbacks and the io-thread registers one.  I think you 
should probably just issue vm_stop(EXCP_DEBUG) from kvm_debug.

Regards,

Anthony Liguori

>      return 1;
>  }
>  
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2008-05-23  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23  0:09 [PATCH] kvm-qemu: Proper vm_stop on debug events Jan Kiszka
2008-05-23  0:35 ` Anthony Liguori [this message]
2008-05-23  2:10   ` Jan Kiszka

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=48361154.4080805@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --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.