summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/boot/1898883
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/gemma3:12b/boot/1898883')
-rw-r--r--results/classifier/gemma3:12b/boot/189888310
1 files changed, 10 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/boot/1898883 b/results/classifier/gemma3:12b/boot/1898883
new file mode 100644
index 000000000..7d9ee2db2
--- /dev/null
+++ b/results/classifier/gemma3:12b/boot/1898883
@@ -0,0 +1,10 @@
+
+qemu-system-riscv64 failed to load binary kernel into memory
+
+QEMU Version: 5.1.0
+Compiled in Ubuntu 20.04 for riscv64, following the guide https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html.
+
+In qemu-system-riscv64, code at 0x80000000 will be executed by virtual CPU.
+For example, using `qemu-system-riscv64 -nographic -machine virt -bios none -kernel vmlinux -S -s`, my homebrew kernel(ELF file) will load at 0x80000000. If I strip the kernel using `riscv64-linux-gnu-objcopy -O binary vmlinux Image`, qemu-system-riscv64 will not load the binary machine code into the riscv64 load address, but `-bios Image` will.
+
+In `qemu-system-aarch64` compiled by Ubuntu team, I can use `qemu-system-aarch64 -M raspi3 -kernel Image_aarch64 -S -s` to load a specific machine code binary into 0x80000. And the elf kernel can be loaded to that address, too.
\ No newline at end of file