From: "Alex Bennée" <alex.bennee@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-riscv@nongnu.org, alistair.francis@wdc.com,
"Bin Meng" <bin.meng@windriver.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Bin Meng" <bmeng@tinylab.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 07/10] hw/riscv/boot.c: use MachineState in riscv_load_initrd()
Date: Thu, 29 Dec 2022 14:17:51 +0000 [thread overview]
Message-ID: <87r0wipa2q.fsf@linaro.org> (raw)
In-Reply-To: <70a0cd63-48e0-a79b-995b-fd34104c64a6@ventanamicro.com>
Daniel Henrique Barboza <dbarboza@ventanamicro.com> writes:
> On 12/28/22 12:51, Philippe Mathieu-Daudé wrote:
>> On 28/12/22 14:33, Daniel Henrique Barboza wrote:
>>> 'filename', 'mem_size' and 'fdt' from riscv_load_initrd() can all be
>>> retrieved by the MachineState object for all callers.
>>>
>>> Cc: Palmer Dabbelt <palmer@dabbelt.com>
>>> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>> Reviewed-by: Bin Meng <bmeng@tinylab.org>
>>> ---
>>> hw/riscv/boot.c | 6 ++++--
>>> hw/riscv/microchip_pfsoc.c | 3 +--
>>> hw/riscv/sifive_u.c | 3 +--
>>> hw/riscv/spike.c | 3 +--
>>> hw/riscv/virt.c | 3 +--
>>> include/hw/riscv/boot.h | 3 +--
>>> 6 files changed, 9 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/hw/riscv/boot.c b/hw/riscv/boot.c
>>> index d3c71b3f0b..f7e806143a 100644
>>> --- a/hw/riscv/boot.c
>>> +++ b/hw/riscv/boot.c
>>> @@ -204,9 +204,11 @@ target_ulong riscv_load_kernel(const char *kernel_filename,
>>> exit(1);
>>> }
>>> -void riscv_load_initrd(const char *filename, uint64_t mem_size,
>>> - uint64_t kernel_entry, void *fdt)
>>> +void riscv_load_initrd(MachineState *machine, uint64_t kernel_entry)
>>> {
>>> + const char *filename = machine->initrd_filename;
>>
>> Do we want to check for missing -initrd here? Or simply return quietly
>> if not provided?
>
> This function is always called after a "if (!machine->initrd_filename)", so we can
> be certain that -initrd will always be present if the function is
> called.
If that is an API guarantee we should assert that is the case then as
calling without machine->initrd_filename would be a bug.
>
> Perhaps one thing that we could do is to remove this check and fold it inside the
> function, right at the start, to make the function behavior independent of what
> the caller is doing. We could do that at patch 9/10 where we'll end up with a single
> caller instead of 4-5.
>
>
> Daniel
>
>>
>>> + uint64_t mem_size = machine->ram_size;
>>> + void *fdt = machine->fdt;
>>> hwaddr start, end;
>>> ssize_t size;
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2022-12-29 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 13:33 [PATCH v3 00/10] irscv: OpenSBI boot test and cleanups Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 01/10] tests/avocado: add RISC-V opensbi boot test Daniel Henrique Barboza
2022-12-28 15:18 ` Bin Meng
2022-12-28 20:21 ` Daniel Henrique Barboza
2022-12-29 11:18 ` Bin Meng
2022-12-28 13:33 ` [PATCH v3 02/10] hw/riscv/spike: use 'fdt' from MachineState Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 03/10] hw/riscv/sifive_u: " Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 04/10] hw/riscv/spike.c: load initrd right after riscv_load_kernel() Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 05/10] hw/riscv: write initrd 'chosen' FDT inside riscv_load_initrd() Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 06/10] hw/riscv: write bootargs 'chosen' FDT after riscv_load_kernel() Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 07/10] hw/riscv/boot.c: use MachineState in riscv_load_initrd() Daniel Henrique Barboza
2022-12-28 15:51 ` Philippe Mathieu-Daudé
2022-12-28 19:04 ` Daniel Henrique Barboza
2022-12-29 14:17 ` Alex Bennée [this message]
2022-12-28 13:33 ` [PATCH v3 08/10] hw/riscv/boot.c: use MachineState in riscv_load_kernel() Daniel Henrique Barboza
2022-12-28 13:33 ` [PATCH v3 09/10] hw/riscv/boot.c: introduce riscv_load_kernel_and_initrd() Daniel Henrique Barboza
2022-12-28 15:52 ` Philippe Mathieu-Daudé
2022-12-28 13:33 ` [PATCH v3 10/10] hw/riscv/boot.c: make riscv_load_initrd() static Daniel Henrique Barboza
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=87r0wipa2q.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--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 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).