[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH v4 4/5] arm: boot: set boot_info starting from first
From: |
Igor Mammedov |
Subject: |
[Qemu-devel] [PATCH v4 4/5] arm: boot: set boot_info starting from first_cpu |
Date: |
Tue, 1 May 2018 15:44:57 +0200 |
Even though nothing is currently broken (since all boards
use first_cpu as boot cpu), make sure that boot_info is set
on all CPUs.
If some board would like support heterogenuos setup (i.e.
init boot_info on subset of CPUs) in future, it should add
a reasonable API to do it, instead of starting assigning
boot_info from some CPU and till the end of present CPUs
list.
Ref:
"Message-ID: <address@hidden>"
Signed-off-by: Igor Mammedov <address@hidden>
Reviewed-by: Peter Maydell <address@hidden>
---
hw/arm/boot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index ad71dd4..144abbd 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -1139,7 +1139,7 @@ void arm_load_kernel(ARMCPU *cpu, struct arm_boot_info
*info)
}
info->is_linux = is_linux;
- for (cs = CPU(cpu); cs; cs = CPU_NEXT(cs)) {
+ for (cs = first_cpu; cs; cs = CPU_NEXT(cs)) {
ARM_CPU(cs)->env.boot_info = info;
}
--
2.7.4
- [Qemu-devel] [PATCH v3 0/5] arm: isolate and clean up dtb generation, Igor Mammedov, 2018/05/01
- [Qemu-devel] [PATCH v3 5/5] make sure that we aren't overwriting mc->get_hotplug_handler by accident, Igor Mammedov, 2018/05/01
- [Qemu-devel] [PATCH v3 2/5] platform-bus-device: use device plug callback instead of machine_done notifier, Igor Mammedov, 2018/05/01
- [Qemu-devel] [PATCH v3 3/5] arm/boot: split load_dtb() from arm_load_kernel(), Igor Mammedov, 2018/05/01
- Re: [Qemu-devel] [PATCH v3 0/5] arm: isolate and clean up dtb generation, Peter Maydell, 2018/05/03