From: Sam Mendoza-Jonas <sam.mj@au1.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V5] spapr: Fix stale HTAB during live migration
Date: Tue, 26 Aug 2014 13:40:31 +1000 [thread overview]
Message-ID: <53FC01AF.2070404@au1.ibm.com> (raw)
In-Reply-To: <20140826030119.GM9923@voom.redhat.com>
On 26/08/14 13:01, David Gibson wrote:
> On Fri, Aug 22, 2014 at 10:24:10AM +1000, Samuel Mendoza-Jonas wrote:
>> If a guest reboots during a running migration, changes to the
>> hash page table are not necessarily updated on the destination.
>> Opening a new file descriptor to the HTAB forces the migration
>> handler to resend the entire table.
>
> Of course, arguably this is a kernel bug - the htab fd should probably
> start re-reporting things if the htab reset ioctl() is called. But I
> guess we need a workaround for existing kernels anyway.
That's right, but as you say it would be nice to cover existing kernels.
>
> However, don't we still have the bug for TCG mode? spapr_reset_htab()
> just memset()s the whole hashtable in that case, which will actually
> clear all the dirty bits, whereas we need to set them.
>
True! I'll add a case for this, it should just be a matter of
checking & setting htab_first_pass.
--
Regards,
Sam Mendoza-Jonas
-----------
LTC Ozlabs
IBM
prev parent reply other threads:[~2014-08-26 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 0:24 [Qemu-devel] [PATCH V5] spapr: Fix stale HTAB during live migration Samuel Mendoza-Jonas
2014-08-26 3:01 ` David Gibson
2014-08-26 3:40 ` Sam Mendoza-Jonas [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=53FC01AF.2070404@au1.ibm.com \
--to=sam.mj@au1.ibm.com \
--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).