[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 4/5] arm: boot: set boot_info starting from f
|
From: |
Peter Maydell |
|
Subject: |
Re: [Qemu-devel] [PATCH v4 4/5] arm: boot: set boot_info starting from first_cpu |
|
Date: |
Thu, 3 May 2018 16:03:09 +0100 |
On 1 May 2018 at 14:44, Igor Mammedov <address@hidden> wrote:
> 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.
It's a bit confusing to only send one patch rather than the
whole set -- our automated patch application and testing
tooling gets confused. I noticed this one by chance because
I was skimming the commit log for v3 and noticed that it was
missing this text. If the change had been in code rather than
in the commit message I would probably not have picked it up...
thanks
-- PMM
- [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