From: Ryan Harper <ryanh@us.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] don't use a 32-bit bit type as offset argument.
Date: Wed, 13 May 2009 15:23:57 -0500 [thread overview]
Message-ID: <20090513202357.GZ3233@us.ibm.com> (raw)
In-Reply-To: <1242242474-7599-1-git-send-email-glommer@redhat.com>
* Glauber Costa <glommer@redhat.com> [2009-05-13 14:22]:
> In the call path of kvm_get_dirty_pages_log_range(),
> its caller kvm_get_dirty_bitmap_cb() passes the
> target_phys_addr_t both as start_addr and the offset.
> So, using int will make dirty tracking over 4G fail
> completely.
Does this patch fix someting like 32-bit migration with >4G ? Seems
like it might.
>
> Of course we should be using qemu types in
> here, so please don't get me started on this. The whole
> file is wrong already ;)
>
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> ---
> qemu-kvm.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/qemu-kvm.c b/qemu-kvm.c
> index f55cee8..27c37b5 100644
> --- a/qemu-kvm.c
> +++ b/qemu-kvm.c
> @@ -1201,7 +1201,7 @@ int kvm_physical_memory_set_dirty_tracking(int enable)
> /* get kvm's dirty pages bitmap and update qemu's */
> static int kvm_get_dirty_pages_log_range(unsigned long start_addr,
> unsigned char *bitmap,
> - unsigned int offset,
> + unsigned long offset,
> unsigned long mem_size)
> {
> unsigned int i, j, n=0;
> --
> 1.5.6.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2009-05-13 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 19:21 [PATCH] don't use a 32-bit bit type as offset argument Glauber Costa
2009-05-13 20:23 ` Ryan Harper [this message]
2009-05-13 20:36 ` Glauber Costa
2009-05-13 21:43 ` Anthony Liguori
2009-05-14 12:16 ` Avi Kivity
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=20090513202357.GZ3233@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.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.