All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: sync from kvm state before generating output
Date: Thu, 15 Jan 2009 14:35:05 -0600	[thread overview]
Message-ID: <496F9DF9.4090605@codemonkey.ws> (raw)
In-Reply-To: <496DFA06.3080709@siemens.com>

Jan Kiszka wrote:
> [ Also available via git://git.kiszka.org/qemu.git queue/gdb ]
>
> Ported from the KVM tree: Synchronize the qemu cpu state with kvm's
> before invoking various monitor info commands (like 'info registers').
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>   

This depends on your previous patch so when you resubmit the previous 
one, please include this in the series and I'll apply both.

Regards,

Anthony Liguori

> ---
>
>  monitor.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index 7ff9890..5a040b4 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -297,6 +297,8 @@ static CPUState *mon_get_cpu(void)
>      if (!mon_cpu) {
>          mon_set_cpu(0);
>      }
> +    if (kvm_enabled())
> +        kvm_get_registers(mon_cpu);
>      return mon_cpu;
>  }
>  
> @@ -323,6 +325,8 @@ static void do_info_cpus(void)
>      mon_get_cpu();
>  
>      for(env = first_cpu; env != NULL; env = env->next_cpu) {
> +        if (kvm_enabled())
> +            kvm_get_registers(env);
>          term_printf("%c CPU #%d:",
>                      (env == mon_cpu) ? '*' : ' ',
>                      env->cpu_index);
>
>
>   

      reply	other threads:[~2009-01-15 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 14:43 [Qemu-devel] [PATCH] monitor: sync from kvm state before generating output Jan Kiszka
2009-01-15 20:35 ` Anthony Liguori [this message]

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=496F9DF9.4090605@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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.