From: Stafford Horne <shorne@gmail.com>
To: QEMU Development <qemu-devel@nongnu.org>
Cc: Stafford Horne <shorne@gmail.com>, Jia Liu <proljc@gmail.com>
Subject: [PATCH 4/4] hw/openrisc/openrisc_sim: Add support for initrd loading
Date: Thu, 10 Feb 2022 15:30:09 +0900 [thread overview]
Message-ID: <20220210063009.1048751-5-shorne@gmail.com> (raw)
In-Reply-To: <20220210063009.1048751-1-shorne@gmail.com>
The loaded initrd is loaded into memory. It's location and size is then
added to the device tree so the kernel knows where to find it.
Signed-off-by: Stafford Horne <shorne@gmail.com>
---
hw/openrisc/openrisc_sim.c | 32 +++++++++++++++++++++++++++++++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/hw/openrisc/openrisc_sim.c b/hw/openrisc/openrisc_sim.c
index d7c26af82c..5354797e20 100644
--- a/hw/openrisc/openrisc_sim.c
+++ b/hw/openrisc/openrisc_sim.c
@@ -187,6 +187,32 @@ static hwaddr openrisc_load_kernel(ram_addr_t ram_size,
return 0;
}
+static hwaddr openrisc_load_initrd(Or1ksimState *s, const char *filename,
+ hwaddr load_start, uint64_t mem_size)
+{
+ int size;
+ hwaddr start;
+
+ /* We put the initrd right after the kernel; page aligned. */
+ start = TARGET_PAGE_ALIGN(load_start);
+
+ size = load_ramdisk(filename, start, mem_size - start);
+ if (size < 0) {
+ size = load_image_targphys(filename, start, mem_size - start);
+ if (size < 0) {
+ error_report("could not load ramdisk '%s'", filename);
+ exit(1);
+ }
+ }
+
+ qemu_fdt_setprop_cell(s->fdt, "/chosen",
+ "linux,initrd-start", start);
+ qemu_fdt_setprop_cell(s->fdt, "/chosen",
+ "linux,initrd-end", start + size);
+
+ return start + size;
+}
+
static uint32_t openrisc_load_fdt(Or1ksimState *s, hwaddr load_start,
uint64_t mem_size)
{
@@ -198,7 +224,7 @@ static uint32_t openrisc_load_fdt(Or1ksimState *s, hwaddr load_start,
exit(1);
}
- /* We should put fdt right after the kernel */
+ /* We put fdt right after the kernel and/or initrd. */
fdt_addr = ROUND_UP(load_start, 4);
fdt_pack(s->fdt);
@@ -369,6 +395,10 @@ static void openrisc_sim_init(MachineState *machine)
machine->kernel_cmdline);
load_addr = openrisc_load_kernel(ram_size, kernel_filename);
+ if (machine->initrd_filename) {
+ load_addr = openrisc_load_initrd(s, machine->initrd_filename,
+ load_addr, machine->ram_size);
+ }
boot_info.fdt_addr = openrisc_load_fdt(s, load_addr, machine->ram_size);
}
--
2.31.1
prev parent reply other threads:[~2022-02-10 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 6:30 [PATCH 0/4] OpenRISC Device Tree Support Stafford Horne
2022-02-10 6:30 ` [PATCH 1/4] hw/openrisc/openrisc_sim: Create machine state for or1ksim Stafford Horne
2022-02-10 11:05 ` Philippe Mathieu-Daudé via
2022-02-10 12:16 ` Stafford Horne
2022-02-10 6:30 ` [PATCH 2/4] hw/openrisc/openrisc_sim: Paramatarize initialization Stafford Horne
2022-02-10 11:07 ` Philippe Mathieu-Daudé via
2022-02-10 12:18 ` Stafford Horne
2022-02-10 6:30 ` [PATCH 3/4] hw/openrisc/openrisc_sim; Add support for loading a decice tree Stafford Horne
2022-02-10 11:10 ` Philippe Mathieu-Daudé via
2022-02-10 12:34 ` Stafford Horne
2022-02-17 18:18 ` Peter Maydell
2022-02-17 21:39 ` Stafford Horne
2022-02-18 11:46 ` Peter Maydell
2022-02-10 6:30 ` Stafford Horne [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=20220210063009.1048751-5-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=proljc@gmail.com \
--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).