From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: ~rlakshmibai <lakshmi.bai.rajasubramanian@bodhicomputing.com>,
qemu-riscv@nongnu.org,
Alistair Francis <alistair.francis@wdc.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH qemu v2] change the fdt_load_addr variable datatype to handle 64-bit DRAM address
Date: Thu, 22 Jun 2023 15:45:40 -0300 [thread overview]
Message-ID: <da9768b2-84be-5e80-cdfd-ca60bdb48ac9@ventanamicro.com> (raw)
In-Reply-To: <168728374725.24164.15960018589525015764-0@git.sr.ht>
(CC-ing Alistair)
On 6/20/23 14:44, ~rlakshmibai wrote:
> From: Lakshmi Bai Raja Subramanian <lakshmi.bai.rajasubramanian@bodhicomputing.com>
>
> fdt_load_addr is getting overflowed when there is no DRAM at lower 32 bit address space.
> To support pure 64-bit DRAM address, fdt_load_addr variable's data type is changed to uint64_t
> instead of uint32_t.
It's worth mentioning that fdt_load_addr receives the result of
riscv_compute_fdt_addr(), which is an uint64_t.
>
> Signed-off-by: Lakshmi Bai Raja Subramanian <lakshmi.bai.rajasubramanian@bodhicomputing.com>
> ---
Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
> hw/riscv/virt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
> index 95708d890e..c348529ac0 100644
> --- a/hw/riscv/virt.c
> +++ b/hw/riscv/virt.c
> @@ -1244,7 +1244,7 @@ static void virt_machine_done(Notifier *notifier, void *data)
> target_ulong start_addr = memmap[VIRT_DRAM].base;
> target_ulong firmware_end_addr, kernel_start_addr;
> const char *firmware_name = riscv_default_firmware_name(&s->soc[0]);
> - uint32_t fdt_load_addr;
> + uint64_t fdt_load_addr;
> uint64_t kernel_entry = 0;
> BlockBackend *pflash_blk0;
>
next prev parent reply other threads:[~2023-06-22 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:44 [PATCH qemu v2] change the fdt_load_addr variable datatype to handle 64-bit DRAM address ~rlakshmibai
2023-06-22 18:45 ` Daniel Henrique Barboza [this message]
2023-06-23 14:36 ` Lakshmi Bai Raja Subramanian
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=da9768b2-84be-5e80-cdfd-ca60bdb48ac9@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=lakshmi.bai.rajasubramanian@bodhicomputing.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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.