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,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Bin Meng" <bmeng@tinylab.org>
Subject: Re: [PATCH v7 2/3] hw/riscv/boot.c: make riscv_load_initrd() static
Date: Mon, 16 Jan 2023 12:55:48 +1000 [thread overview]
Message-ID: <CAKmqyKOgn3a_Fe7sr75iVsJTMUehRWLTLH0e89vKS--TA2Je2g@mail.gmail.com> (raw)
In-Reply-To: <20230113171805.470252-3-dbarboza@ventanamicro.com>
On Sat, Jan 14, 2023 at 3:39 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> The only remaining caller is riscv_load_kernel_and_initrd() which
> belongs to the same file.
>
> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Bin Meng <bmeng@tinylab.org>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> hw/riscv/boot.c | 80 ++++++++++++++++++++---------------------
> include/hw/riscv/boot.h | 1 -
> 2 files changed, 40 insertions(+), 41 deletions(-)
>
> diff --git a/hw/riscv/boot.c b/hw/riscv/boot.c
> index 4888d5c1e0..e868fb6ade 100644
> --- a/hw/riscv/boot.c
> +++ b/hw/riscv/boot.c
> @@ -173,6 +173,46 @@ target_ulong riscv_load_firmware(const char *firmware_filename,
> exit(1);
> }
>
> +static void riscv_load_initrd(MachineState *machine, uint64_t kernel_entry)
> +{
> + const char *filename = machine->initrd_filename;
> + uint64_t mem_size = machine->ram_size;
> + void *fdt = machine->fdt;
> + hwaddr start, end;
> + ssize_t size;
> +
> + g_assert(filename != NULL);
> +
> + /*
> + * We want to put the initrd far enough into RAM that when the
> + * kernel is uncompressed it will not clobber the initrd. However
> + * on boards without much RAM we must ensure that we still leave
> + * enough room for a decent sized initrd, and on boards with large
> + * amounts of RAM we must avoid the initrd being so far up in RAM
> + * that it is outside lowmem and inaccessible to the kernel.
> + * So for boards with less than 256MB of RAM we put the initrd
> + * halfway into RAM, and for boards with 256MB of RAM or more we put
> + * the initrd at 128MB.
> + */
> + start = kernel_entry + MIN(mem_size / 2, 128 * MiB);
> +
> + size = load_ramdisk(filename, start, mem_size - start);
> + if (size == -1) {
> + size = load_image_targphys(filename, start, mem_size - start);
> + if (size == -1) {
> + error_report("could not load ramdisk '%s'", filename);
> + exit(1);
> + }
> + }
> +
> + /* Some RISC-V machines (e.g. opentitan) don't have a fdt. */
> + if (fdt) {
> + end = start + size;
> + qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-start", start);
> + qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-end", end);
> + }
> +}
> +
> target_ulong riscv_load_kernel(MachineState *machine,
> target_ulong kernel_start_addr,
> bool load_initrd,
> @@ -225,46 +265,6 @@ out:
> return kernel_entry;
> }
>
> -void riscv_load_initrd(MachineState *machine, uint64_t kernel_entry)
> -{
> - const char *filename = machine->initrd_filename;
> - uint64_t mem_size = machine->ram_size;
> - void *fdt = machine->fdt;
> - hwaddr start, end;
> - ssize_t size;
> -
> - g_assert(filename != NULL);
> -
> - /*
> - * We want to put the initrd far enough into RAM that when the
> - * kernel is uncompressed it will not clobber the initrd. However
> - * on boards without much RAM we must ensure that we still leave
> - * enough room for a decent sized initrd, and on boards with large
> - * amounts of RAM we must avoid the initrd being so far up in RAM
> - * that it is outside lowmem and inaccessible to the kernel.
> - * So for boards with less than 256MB of RAM we put the initrd
> - * halfway into RAM, and for boards with 256MB of RAM or more we put
> - * the initrd at 128MB.
> - */
> - start = kernel_entry + MIN(mem_size / 2, 128 * MiB);
> -
> - size = load_ramdisk(filename, start, mem_size - start);
> - if (size == -1) {
> - size = load_image_targphys(filename, start, mem_size - start);
> - if (size == -1) {
> - error_report("could not load ramdisk '%s'", filename);
> - exit(1);
> - }
> - }
> -
> - /* Some RISC-V machines (e.g. opentitan) don't have a fdt. */
> - if (fdt) {
> - end = start + size;
> - qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-start", start);
> - qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-end", end);
> - }
> -}
> -
> uint64_t riscv_load_fdt(hwaddr dram_base, uint64_t mem_size, void *fdt)
> {
> uint64_t temp, fdt_addr;
> diff --git a/include/hw/riscv/boot.h b/include/hw/riscv/boot.h
> index c3de897371..cbd131bad7 100644
> --- a/include/hw/riscv/boot.h
> +++ b/include/hw/riscv/boot.h
> @@ -47,7 +47,6 @@ target_ulong riscv_load_kernel(MachineState *machine,
> target_ulong firmware_end_addr,
> bool load_initrd,
> symbol_fn_t sym_cb);
> -void riscv_load_initrd(MachineState *machine, uint64_t kernel_entry);
> uint64_t riscv_load_fdt(hwaddr dram_start, uint64_t dram_size, void *fdt);
> void riscv_setup_rom_reset_vec(MachineState *machine, RISCVHartArrayState *harts,
> hwaddr saddr,
> --
> 2.39.0
>
>
next prev parent reply other threads:[~2023-01-16 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 17:18 [PATCH v7 0/3] hw/riscv: clear kernel_entry high bits with 32bit CPUs Daniel Henrique Barboza
2023-01-13 17:18 ` [PATCH v7 1/3] hw/riscv/boot.c: consolidate all kernel init in riscv_load_kernel() Daniel Henrique Barboza
2023-01-13 17:18 ` [PATCH v7 2/3] hw/riscv/boot.c: make riscv_load_initrd() static Daniel Henrique Barboza
2023-01-16 2:55 ` Alistair Francis [this message]
2023-01-13 17:18 ` [PATCH v7 3/3] hw/riscv: clear kernel_entry higher bits in load_elf_ram_sym() Daniel Henrique Barboza
2023-01-14 13:40 ` Bin Meng
2023-01-16 4:28 ` Alistair Francis
2023-01-26 12:07 ` Bin Meng
2023-01-29 22:50 ` Alistair Francis
2023-01-16 9:25 ` Philippe Mathieu-Daudé
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=CAKmqyKOgn3a_Fe7sr75iVsJTMUehRWLTLH0e89vKS--TA2Je2g@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.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).