All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [Qemu-devel] Re: [RESEND][PATCH] save/restore interrupt_request across snapshots
Date: Tue, 1 Jul 2008 22:55:00 +0100	[thread overview]
Message-ID: <200807012255.01121.paul@codesourcery.com> (raw)
In-Reply-To: <486AA5DE.1000708@web.de>

On Tuesday 01 July 2008, Jan Kiszka wrote:
> Paul Brook wrote:
> >> Save interrupt_request state along with the cpu snapshot and restore it
> >> properly. This also solves the bug that pending interrupts before
> >> invocation of qemu_loadvm_state can tunnel into the resumed guest,
> >> causing invalid IRQs there.
> >
> > I just checked in a patch which is a superset of this functionality.
>
> Nice cleanups!
>
> ( Well, except for
>
>    if (version_id != 3 && version_id != 4 && version_id != 5
>        && version_id != 6)
>
> :-> )

I was tempted to rip it out altogether, and replace with
  if (version_id != CPU_SAVE_VERSION)
IMHO explicitly enumerating all the versions we claim to be able to load isn't 
a bad thing.

> And after fixing this typo, it also works nicely:
>      qemu_get_be32s(f, &env->halted);
> -    qemu_put_be32s(f, &env->interrupt_request);
> +    qemu_get_be32s(f, &env->interrupt_request);

Good catch, thanks.

Paul

  reply	other threads:[~2008-07-01 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 11:41 [Qemu-devel] [PATCH] save/restore interrupt_request across snapshots Jan Kiszka
2008-07-01 16:21 ` [Qemu-devel] [RESEND][PATCH] " Jan Kiszka
2008-07-01 20:02   ` Paul Brook
2008-07-01 21:47     ` [Qemu-devel] " Jan Kiszka
2008-07-01 21:55       ` Paul Brook [this message]
2008-07-01 22:17   ` [Qemu-devel] " Edgar E. Iglesias

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=200807012255.01121.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=jan.kiszka@web.de \
    --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.