From: Alexander Graf <agraf@suse.de>
To: stefano.stabellini@eu.citrix.com
Cc: peter.maydell@linaro.org, xen-devel@lists.xensource.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu_ram_ptr_length: take ram_addr_t as arguments
Date: Thu, 30 Jun 2011 17:11:16 +0200 [thread overview]
Message-ID: <4E0C9214.80702@suse.de> (raw)
In-Reply-To: <1309195566-29207-1-git-send-email-stefano.stabellini@eu.citrix.com>
On 06/27/2011 07:26 PM, stefano.stabellini@eu.citrix.com wrote:
> From: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
>
> qemu_ram_ptr_length should take ram_addr_t as argument rather than
> target_phys_addr_t because is doing comparisons with RAMBlock addresses.
>
> cpu_physical_memory_map should create a ram_addr_t address to pass to
> qemu_ram_ptr_length from PhysPageDesc phys_offset.
>
> Remove code after abort() in qemu_ram_ptr_length.
>
>
> Changes in v2:
>
> - handle 0 size in qemu_ram_ptr_length;
>
> - rename addr1 to raddr;
>
> - initialize raddr to ULONG_MAX.
>
Thanks, applied to the xen-next branch.
Alex
prev parent reply other threads:[~2011-06-30 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 17:26 [Qemu-devel] [PATCH v2] qemu_ram_ptr_length: take ram_addr_t as arguments stefano.stabellini
2011-06-28 10:52 ` Peter Maydell
2011-06-30 15:11 ` Alexander Graf [this message]
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=4E0C9214.80702@suse.de \
--to=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).