From: Anthony Liguori <aliguori@us.ibm.com>
To: Lei Li <lilei@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: lagarcia@br.ibm.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/7] arch_init: add ram_madvise_free()
Date: Sun, 16 Jun 2013 11:04:34 -0500 [thread overview]
Message-ID: <878v2ahwj1.fsf@codemonkey.ws> (raw)
In-Reply-To: <1371397053-4503-4-git-send-email-lilei@linux.vnet.ibm.com>
Lei Li <lilei@linux.vnet.ibm.com> writes:
> Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
> ---
> arch_init.c | 13 +++++++++++++
> include/migration/migration.h | 3 +++
> 2 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/arch_init.c b/arch_init.c
> index 872020e..fc66bd2 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -524,6 +524,19 @@ uint64_t ram_bytes_total(void)
> return total;
> }
>
> +void ram_madvise_free(ram_addr_t size)
> +{
> + void *ram;
> + RAMBlock *block = NULL;
> +
> + ram = memory_region_get_ram_ptr(block->mr);
> +
> + /* XXX. Here just simplely madvise(.., MADV_DONTNEED) the whole ram
> + * pages, need more work to keep MADV_DONTNEED ram pages that
> + * already sent. */
> + qemu_madvise(ram, size, MADV_DONTNEED);
> +}
> +
I don't think this is right at all. There's no guarantee we have a
single linear mapping of all ram.
I think you need something a bit more clever than this.
> static void migration_end(void)
> {
> if (migration_bitmap) {
> diff --git a/include/migration/migration.h b/include/migration/migration.h
> index 8866c3c..9cc5285 100644
> --- a/include/migration/migration.h
> +++ b/include/migration/migration.h
> @@ -21,6 +21,7 @@
> #include "qapi/error.h"
> #include "migration/vmstate.h"
> #include "qapi-types.h"
> +#include "exec/memory.h"
>
> enum {
> MIG_STATE_ERROR,
> @@ -100,6 +101,8 @@ uint64_t ram_bytes_remaining(void);
> uint64_t ram_bytes_transferred(void);
> uint64_t ram_bytes_total(void);
>
> +void ram_madvise_free(ram_addr_t size);
> +
If you introduce new interfaces, please include documentation in the
header.
Regards,
Anthony Liguori
> extern SaveVMHandlers savevm_ram_handlers;
>
> uint64_t dup_mig_bytes_transferred(void);
> --
> 1.7.7.6
next prev parent reply other threads:[~2013-06-16 16:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 15:37 [Qemu-devel] [PATCH 0/7 RFC] Localhost live migration Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 1/7] migration: export MIG_STATE_xxx flags Lei Li
2013-06-16 16:01 ` Anthony Liguori
2013-06-18 6:03 ` Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 2/7] savevm: export qemu_save_device_state() Lei Li
2013-06-16 16:02 ` Anthony Liguori
2013-06-18 6:05 ` Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 3/7] arch_init: add ram_madvise_free() Lei Li
2013-06-16 16:04 ` Anthony Liguori [this message]
2013-06-18 6:11 ` Lei Li
2013-08-02 19:34 ` Michael R. Hines
2013-06-16 15:37 ` [Qemu-devel] [PATCH 4/7] migration-local: implementation of outgoing part Lei Li
2013-06-16 16:07 ` Anthony Liguori
2013-06-18 6:25 ` Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 5/7] migration-local: implementation of incoming part Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 6/7] migration-local: add option to command line for -incoming-local Lei Li
2013-06-16 15:37 ` [Qemu-devel] [PATCH 7/7] hmp: add hmp_localhost_migration interface Lei Li
2013-06-16 16:01 ` [Qemu-devel] [PATCH 0/7 RFC] Localhost live migration Anthony Liguori
2013-06-18 6:02 ` Lei Li
2013-06-17 12:57 ` Stefan Hajnoczi
2013-06-18 6:01 ` Lei Li
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=878v2ahwj1.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=lagarcia@br.ibm.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).