From: Luca Fancellu <Luca.Fancellu@arm.com>
To: Mark Rutland <Mark.Rutland@arm.com>
Cc: Andre Przywara <Andre.Przywara@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [boot-wrapper v4 4/4] aarch64: Start Xen on Armv8-R at EL2
Date: Tue, 26 Nov 2024 14:40:08 +0000 [thread overview]
Message-ID: <3C2D75A2-1765-4353-95E3-E8AF21EF66A1@arm.com> (raw)
In-Reply-To: <Z0W35oFzkdOaahsv@J2N7QTR9R3>
Hi Mark,
> On 26 Nov 2024, at 11:58, Mark Rutland <mark.rutland@arm.com> wrote:
>
> On Thu, Oct 17, 2024 at 10:55:20AM +0100, Luca Fancellu wrote:
>> When bootwrapper is compiled with Xen support and it is started
>> at EL2 on Armv8-R AArch64, keep the current EL and jump to the
>> Xen image using the SPSR_KERNEL as spsr_el2 value.
>
> What's the plan for booting Xen? i.e. is that using spin-table or PSCI?
>
> I'm hesitant to expose PSCI booting to EL2 on ARMv8-R, because PSCI
> doesn't really support ARMv8-R (the spec says nothing about it, and all
> we're doing is providing the illusion of ARMv8-A to Linux), and Xen
> would have to override the vectors anyway, so it doesn't really make
> sense.
>
> Given the latter part I'm assuming you only care about spin-table for
> Xen, which is less concerning. I think we should make that more explicit
> in the config options and forbid the combination of ARMv8-R + PSCI +
> Xen.
Yes, I only care about spin-table at the moment, would this diff on top of this
patch be ok for you in order to enforce that?
diff --git a/configure.ac b/configure.ac
index a433c89bd2ae..a16bc25508f3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -115,6 +115,11 @@ AS_IF([test "x$USE_PSCI" != "xyes" -a "x$KERNEL_ES" = "x32"],
[AC_MSG_ERROR([With an AArch32 kernel, boot method must be PSCI.])]
)
+# Don't allow PSCI + Xen + aarch64-r
+AS_IF([test "x$USE_PSCI" = "xyes" -a "x$USE_ARCH" = "xaarch64-r" -a "x$X_IMAGE" != "x"],
+ [AC_MSG_ERROR([With aarch64-r and Xen, PSCI must be disabled.])]
+)
+
# Allow a user to pass --with-initrd
AC_ARG_WITH([initrd],
AS_HELP_STRING([--with-initrd], [embed an initrd in the kernel image]),
Cheers,
Luca
next prev parent reply other threads:[~2024-11-26 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:55 [boot-wrapper v4 0/4] Add Armv8-R AArch64 support Luca Fancellu
2024-10-17 9:55 ` [boot-wrapper v4 1/4] Introduce --with-bw-arch for boot-wrapper compile arch Luca Fancellu
2024-10-17 9:55 ` [boot-wrapper v4 2/4] aarch64: Enable Armv8-R EL2 boot Luca Fancellu
2024-10-17 9:55 ` [boot-wrapper v4 3/4] aarch64: Implement PSCI for Armv8-R Luca Fancellu
2024-10-17 9:55 ` [boot-wrapper v4 4/4] aarch64: Start Xen on Armv8-R at EL2 Luca Fancellu
2024-11-26 11:58 ` Mark Rutland
2024-11-26 14:40 ` Luca Fancellu [this message]
2024-11-26 11:54 ` [boot-wrapper v4 0/4] Add Armv8-R AArch64 support Mark Rutland
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=3C2D75A2-1765-4353-95E3-E8AF21EF66A1@arm.com \
--to=luca.fancellu@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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