From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RESEND][PATCH] save/restore interrupt_request across snapshots
Date: Tue, 01 Jul 2008 23:47:10 +0200 [thread overview]
Message-ID: <486AA5DE.1000708@web.de> (raw)
In-Reply-To: <200807012102.25714.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
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)
:-> )
And after fixing this typo, it also works nicely:
Index: exec.c
===================================================================
--- exec.c (Revision 4817)
+++ exec.c (Arbeitskopie)
@@ -463,7 +463,7 @@ static int cpu_common_load(QEMUFile *f,
return -EINVAL;
qemu_get_be32s(f, &env->halted);
- qemu_put_be32s(f, &env->interrupt_request);
+ qemu_get_be32s(f, &env->interrupt_request);
tlb_flush(env, 1);
return 0;
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-07-01 21:47 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 ` Jan Kiszka [this message]
2008-07-01 21:55 ` [Qemu-devel] " Paul Brook
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=486AA5DE.1000708@web.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).