From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@petalogix.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 1/6] hw/arm_boot.c: Make ram_size a target_phys_addr_t
Date: Fri, 06 Jul 2012 15:48:56 +0200 [thread overview]
Message-ID: <4FF6ECC8.9000100@suse.de> (raw)
In-Reply-To: <1341507652-22155-2-git-send-email-peter.maydell@linaro.org>
Am 05.07.2012 19:00, schrieb Peter Maydell:
> Make the RAM size in arm_boot_info a target_phys_addr_t so
> it can express RAM sizes up to the limit imposed by the
> physical address size.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> hw/arm-misc.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/arm-misc.h b/hw/arm-misc.h
> index 1f96229..c313027 100644
> --- a/hw/arm-misc.h
> +++ b/hw/arm-misc.h
> @@ -25,7 +25,7 @@ qemu_irq *armv7m_init(MemoryRegion *address_space_mem,
>
> /* arm_boot.c */
> struct arm_boot_info {
> - int ram_size;
> + target_phys_addr_t ram_size;
> const char *kernel_filename;
> const char *kernel_cmdline;
> const char *initrd_filename;
Didn't we conclude in lengthy and emotional discussions that int64_t was
the best compromise to solve the highbank and pseries image loading issues?
What I still dislike about target_phys_addr_t is that "ram_size" is not
an address but a size.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-07-06 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 17:00 [Qemu-devel] [PATCH 0/6] arm_boot/vexpress-a15: Support >4GB of RAM Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 1/6] hw/arm_boot.c: Make ram_size a target_phys_addr_t Peter Maydell
2012-07-06 1:58 ` Peter Crosthwaite
2012-07-06 13:48 ` Andreas Färber [this message]
2012-07-06 13:54 ` Alexander Graf
2012-07-06 14:02 ` Andreas Färber
2012-07-06 14:04 ` Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 2/6] hw/arm_boot.c: Consistently use ram_size from arm_boot_info struct Peter Maydell
2012-07-06 2:00 ` Peter Crosthwaite
2012-07-06 7:23 ` Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 3/6] hw/arm_boot.c: Check for RAM sizes exceeding ATAGS capacity Peter Maydell
2012-07-06 2:05 ` Peter Crosthwaite
2012-07-06 7:25 ` Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 4/6] device_tree: Add support for reading device tree properties Peter Maydell
2012-07-06 1:56 ` Peter Crosthwaite
2012-07-06 7:18 ` Peter Maydell
2012-07-06 15:34 ` Peter Maydell
2012-07-06 15:44 ` Peter Maydell
2012-07-10 6:54 ` Peter Crosthwaite
2012-07-10 7:52 ` Peter Maydell
2012-07-10 13:03 ` Peter Maydell
2012-07-13 1:24 ` Peter Crosthwaite
2012-07-05 17:00 ` [Qemu-devel] [PATCH 5/6] hw/arm_boot.c: Support DTBs which use 64 bit addresses Peter Maydell
2012-07-05 18:53 ` Blue Swirl
2012-07-05 19:26 ` Peter Maydell
2012-07-06 2:19 ` Peter Crosthwaite
2012-07-05 17:00 ` [Qemu-devel] [PATCH 6/6] hw/vexpress.c: Allow >4GB of RAM for Cortex-A15 daughterboard Peter Maydell
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=4FF6ECC8.9000100@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=patches@linaro.org \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--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 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).