From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Clément Chigot" <chigot@adacore.com>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, peter.maydell@linaro.org,
edgar.iglesias@gmail.com, alistair@alistair23.me
Subject: Re: [PATCH v3 1/3] hw/arm: make cpu targeted by arm_load_kernel the primary CPU.
Date: Mon, 16 Jun 2025 07:44:50 +0200 [thread overview]
Message-ID: <23605427-8930-41a8-bd92-6a3a76a950cf@linaro.org> (raw)
In-Reply-To: <20250613134208.1509436-2-chigot@adacore.com>
On 13/6/25 15:42, Clément Chigot wrote:
> Currently, arm booting processus assumes that the first_cpu is the CPU
> that will boot: `arm_load_kernel` is powering off all but the `first_cpu`;
> `do_cpu_reset` is setting the loader address only for this `first_cpu`.
>
> For most of the boards, this isn't an issue as the kernel is loaded and
> booted on the first CPU anyway. However, for zynqmp, the option
> "boot-cpu" allows to choose any CPUs.
>
> Create a new arm_boot_info entry `primary_cpu` recording which CPU will
> be boot first. This one is set when `arm_boot_kernel` is called.
>
> Signed-off-by: Clément Chigot <chigot@adacore.com>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> hw/arm/boot.c | 15 +++++++--------
> include/hw/arm/boot.h | 3 +++
> 2 files changed, 10 insertions(+), 8 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-06-16 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 13:42 [PATCH v3 0/3] xlnx-zynqmp: add support to boot on RPUs Clément Chigot
2025-06-13 13:42 ` [PATCH v3 1/3] hw/arm: make cpu targeted by arm_load_kernel the primary CPU Clément Chigot
2025-06-16 5:44 ` Philippe Mathieu-Daudé [this message]
2025-06-13 13:42 ` [PATCH v3 2/3] hw/intc/arm_gic: introduce a first-cpu-index property Clément Chigot
2025-06-13 13:42 ` [PATCH v3 3/3] hw/arm/xlnx-zynqmp: wire a second GIC for the Cortex-R5 Clément Chigot
2025-08-25 9:50 ` Clément Chigot
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=23605427-8930-41a8-bd92-6a3a76a950cf@linaro.org \
--to=philmd@linaro.org \
--cc=alistair@alistair23.me \
--cc=chigot@adacore.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).