[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 13/18] arch_init: adjust ram_save_setup() for mi
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH 13/18] arch_init: adjust ram_save_setup() for migrate_is_localhost |
Date: |
Fri, 23 Aug 2013 10:06:03 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 |
Il 23/08/2013 09:57, Alex Bligh ha scritto:
>
>
> --On 23 August 2013 09:48:42 +0200 Paolo Bonzini <address@hidden>
> wrote:
>
>> As a matter of fact, 2^28 madvise system calls will take much, much
>> longer than 100ms.
>
> Probably a stupid question, but why would you need to do one call per
> page? It takes a 'size_t length' parameter.
Right now migration is done a page at a time, and so is madvise AFAIU.
However, even with a larger length parameter I suspect it would alone
take more than 2 cycles per page.
So one way to do this could be to add a flag to "migrate" that would
migrate devices only, and use shared memory in both the source and the
target.
There is still a problem, because we must make sure the destination
doesn't write to memory (e.g. read firmware) when initializing the
board, because that would overwrite the memory of the running instance.
But it looks more promising than page flipping.
Paolo
- [Qemu-devel] [PATCH 14/18] arch_init: skip migration_bitmap_sync for local migration, (continued)
[Qemu-devel] [PATCH 17/18] migration: add prefix for local migration to incoming migration, Lei Li, 2013/08/21
[Qemu-devel] [PATCH 16/18] migration-local: implementation of incoming part, Lei Li, 2013/08/21
[Qemu-devel] [PATCH 18/18] hmp: better fomat for info migrate_capabilities, Lei Li, 2013/08/21