From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, liwei1518@gmail.com,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
joel@jms.id.au
Subject: Re: [PATCH v2 0/9] hw/riscv/virt.c: memmap usage cleanup
Date: Thu, 1 May 2025 10:33:08 +1000 [thread overview]
Message-ID: <CAKmqyKOc+X4ZgPq3SDfUEKPGksOJaaC8UfbrnqNptFv+yv2AmA@mail.gmail.com> (raw)
In-Reply-To: <20250429125811.224803-1-dbarboza@ventanamicro.com>
On Tue, Apr 29, 2025 at 11:00 PM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> In this new version a small change was made in patch 9 after
> discussions with Joel during v1 [1]. The idea is that we want to be
> consistent (as close as we can) with the idea that a
> memory address is a hwaddr type.
>
> This new version does not conflict with "hw/riscv/virt: device tree reg
> cleanups" from Joel [2].
>
> No other changes made. Patches based on alistair/riscv-to-apply.next.
>
> Changes from v2:
> - patch 9:
> - in create_fdt_socket_memory(), change 'addr' to hwaddr and use the
> HWADDR_PRIx fmt type
> - v1 link: https://lore.kernel.org/qemu-riscv/20250423110630.2249904-1-dbarboza@ventanamicro.com/
>
> [1] https://lore.kernel.org/qemu-riscv/d404d535-fc04-43ac-a7a7-2f216cad993c@ventanamicro.com/
> [2] https://lore.kernel.org/qemu-riscv/20250429061223.1457166-1-joel@jms.id.au/
>
> Daniel Henrique Barboza (9):
> hw/riscv/virt.c: enforce s->memmap use in machine_init()
> hw/riscv/virt.c: remove trivial virt_memmap references
> hw/riscv/virt.c: use s->memmap in virt_machine_done()
> hw/riscv/virt.c: add 'base' arg in create_fw_cfg()
> hw/riscv/virt.c: use s->memmap in create_fdt() path
> hw/riscv/virt.c: use s->memmap in create_fdt_sockets() path
> hw/riscv/virt.c: use s->memmap in create_fdt_virtio()
> hw/riscv/virt.c: use s->memmap in finalize_fdt() functions
> hw/riscv/virt.c: remove 'long' casts in fmt strings
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> hw/riscv/virt.c | 272 +++++++++++++++++++++++++-----------------------
> 1 file changed, 140 insertions(+), 132 deletions(-)
>
> --
> 2.49.0
>
>
prev parent reply other threads:[~2025-05-01 0:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 12:58 [PATCH v2 0/9] hw/riscv/virt.c: memmap usage cleanup Daniel Henrique Barboza
2025-04-29 12:58 ` [PATCH v2 1/9] hw/riscv/virt.c: enforce s->memmap use in machine_init() Daniel Henrique Barboza
2025-04-29 12:58 ` [PATCH v2 2/9] hw/riscv/virt.c: remove trivial virt_memmap references Daniel Henrique Barboza
2025-04-30 23:59 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 3/9] hw/riscv/virt.c: use s->memmap in virt_machine_done() Daniel Henrique Barboza
2025-05-01 0:02 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 4/9] hw/riscv/virt.c: add 'base' arg in create_fw_cfg() Daniel Henrique Barboza
2025-05-01 0:03 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 5/9] hw/riscv/virt.c: use s->memmap in create_fdt() path Daniel Henrique Barboza
2025-05-01 0:08 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 6/9] hw/riscv/virt.c: use s->memmap in create_fdt_sockets() path Daniel Henrique Barboza
2025-05-01 0:10 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 7/9] hw/riscv/virt.c: use s->memmap in create_fdt_virtio() Daniel Henrique Barboza
2025-05-01 0:11 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 8/9] hw/riscv/virt.c: use s->memmap in finalize_fdt() functions Daniel Henrique Barboza
2025-05-01 0:12 ` Alistair Francis
2025-04-29 12:58 ` [PATCH v2 9/9] hw/riscv/virt.c: remove 'long' casts in fmt strings Daniel Henrique Barboza
2025-05-01 0:13 ` Alistair Francis
2025-05-01 0:33 ` Alistair Francis [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=CAKmqyKOc+X4ZgPq3SDfUEKPGksOJaaC8UfbrnqNptFv+yv2AmA@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=joel@jms.id.au \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).