All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] postcopy: Require RAMBlocks that are whole pages
Date: Wed, 17 May 2017 21:29:09 +0200	[thread overview]
Message-ID: <87bmqrb7ui.fsf@secure.mitica> (raw)
In-Reply-To: <20170517165810.18164-3-dgilbert@redhat.com> (David Alan Gilbert's message of "Wed, 17 May 2017 17:58:10 +0100")

"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> It turns out that it's legal to create a VM with RAMBlocks that aren't
> a multiple of the pagesize in use; e.g. a 1025M main memory using
> 2M host pages.  That breaks postcopy's atomic placement of pages,
> so disallow it.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

Reviewed-by: Juan Quintela <quintela@redhat.com>


>      }
>  
>      /* We don't support postcopy with shared RAM yet */
> -    if (qemu_ram_foreach_block(test_range_shared, NULL)) {
> +    if (qemu_ram_foreach_block(test_ramblock_postcopiable, NULL)) {

When I was looking at this code, I still don't know why
qemu_ram_foreach_block() don't pass the block directly.  It needs it
almost all callers.

When I saw it I was about to change it, but got sidetracked on other
things :-p

Later, Juan.

  reply	other threads:[~2017-05-17 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 16:58 [Qemu-devel] [PATCH 0/2] Migration+huge page fixes Dr. David Alan Gilbert (git)
2017-05-17 16:58 ` [Qemu-devel] [PATCH 1/2] migration: Fix non-multiple of page size migration Dr. David Alan Gilbert (git)
2017-05-17 19:27   ` Juan Quintela
2017-05-17 16:58 ` [Qemu-devel] [PATCH 2/2] postcopy: Require RAMBlocks that are whole pages Dr. David Alan Gilbert (git)
2017-05-17 19:29   ` Juan Quintela [this message]
2017-05-18  8:08     ` Dr. David Alan Gilbert
2017-05-19  4:00       ` Peter Xu

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=87bmqrb7ui.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.