[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] kvm: Mark full address range dirty on live migr
Re: [Qemu-devel] [PATCH] kvm: Mark full address range dirty on live migration start
Sat, 23 May 2009 15:47:03 +0200
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:18.104.22.168) Gecko/20080226 SUSE/22.214.171.124-1.1 Thunderbird/126.96.36.199 Mnenhy/0.7.5.666
Glauber Costa wrote:
> On Fri, May 22, 2009 at 11:51:45PM +0200, Jan Kiszka wrote:
>> As Avi correctly noted, last_ram_offset does not mark the last physical
>> RAM address the guest may see (due to non-continuous memory regions).
>> Ensure that we catch them all by marking the full possible address range
>> Signed-off-by: Jan Kiszka <address@hidden>
> Indeed, we already do something in that lines in qemu-kvm tree,
> in a place that does not apply for It makes a lot of sense. Just
> maybe you could just -1UL instead of defining a new constant, but I don't
> really care.
I intentionally made this verbose.
> As soon as this is applied to master, I'll pick it for stable too.
Migration for KVM would be a new feature for stable. It requires a new
CPU save/restore format (V9). Do think that qualifies it for stable.
Description: OpenPGP digital signature