From: Alexander Graf <agraf@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, aik@ozlabs.ru,
"david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes
Date: Sun, 20 Sep 2015 22:31:01 +0200 [thread overview]
Message-ID: <55FF1785.6070801@suse.de> (raw)
In-Reply-To: <1442259039-22137-1-git-send-email-mark.cave-ayland@ilande.co.uk>
On 14.09.15 21:30, Mark Cave-Ayland wrote:
> Whilst trying to fix migration of g3beige/mac99 images I came up with the
> following patchset. The first patch is really cosmetic, while the second patch
> alters the migration stream to include internal CPU IRQ state which appears
> to fix an issue where images randomly fail to resume after migration.
>
> As the second patch would need more work if deemed correct (the change in
> migration stream would require a bump in version number), it seemed worth
> putting this out for review in case this is actually the symptom of another
> bug.
>
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
David, when a non-RFC version of this patch comes around, could you
please review and if good apply it to the tree via your branch?
Thanks a bunch!
Alex
next prev parent reply other threads:[~2015-09-20 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 19:30 [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes Mark Cave-Ayland
2015-09-14 19:30 ` [Qemu-devel] [RFC PATCH 1/2] target-ppc: remove hreg_compute_mem_idx() from cpu_post_load Mark Cave-Ayland
2015-09-14 23:25 ` Alexey Kardashevskiy
2015-09-14 19:30 ` [Qemu-devel] [RFC PATCH 2/2] target-ppc: add CPU IRQ state to PPC VMStateDescription Mark Cave-Ayland
2015-09-14 23:10 ` Alexey Kardashevskiy
2015-09-15 21:09 ` Mark Cave-Ayland
2015-09-17 4:32 ` Alexey Kardashevskiy
2015-09-20 20:31 ` Alexander Graf [this message]
2015-10-23 1:46 ` [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes david
2015-10-23 19:22 ` Mark Cave-Ayland
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=55FF1785.6070801@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).