qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: "david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes
Date: Fri, 23 Oct 2015 20:22:00 +0100	[thread overview]
Message-ID: <562A88D8.7060800@ilande.co.uk> (raw)
In-Reply-To: <20151023014632.GC27149@voom.redhat.com>

On 23/10/15 02:46, david@gibson.dropbear.id.au wrote:

> On Sun, Sep 20, 2015 at 10:31:01PM +0200, Alexander Graf wrote:
>>
>>
>> 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!
> 
> Mark,
> 
> I haven't seen a revised version of this.  Is that because it hasn't
> been posted, or just because I've missed it somehow?

Hi David,

I've spent a bit more time on this, and even with the patch I'm still
seeing migration issues which need further investigation so I'll have to
pick this up again after the upcoming release. On the plus side I've
been able to spend some time this week updating Cormac's OS9 GSoC
patches for upstream, so I'd be grateful if you could take a look at
those in the meantime.


ATB,

Mark.

      reply	other threads:[~2015-10-23 19:22 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 ` [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes Alexander Graf
2015-10-23  1:46   ` david
2015-10-23 19:22     ` Mark Cave-Ayland [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=562A88D8.7060800@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --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).