From: Michal Orzel <michal.orzel@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: Michal Orzel <michal.orzel@amd.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
Wei Liu <wl@xen.org>
Subject: [PATCH] SUPPORT.md: clarify support of booting 32-bit Xen on ARMv8
Date: Thu, 29 Feb 2024 13:13:52 +0100 [thread overview]
Message-ID: <20240229121352.11264-1-michal.orzel@amd.com> (raw)
Since commit bd1001db0af1 ("xen/arm: arm32: Allow Xen to boot on
unidentified CPUs"), it's been possible to boot 32-bit Xen on ARMv8A CPUs
in AArch32 state (assuming HW supports EL2 execution in AArch32). Clarify
the support statement and mark it as Tech Preview, as this use case is
uncommon and hasn't really been tested/hardened.
Signed-off-by: Michal Orzel <michal.orzel@amd.com>
---
SUPPORT.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/SUPPORT.md b/SUPPORT.md
index a90d1108c9d9..acc61230bb5e 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -40,6 +40,7 @@ supported in this document.
Status: Supported
Status, Cortex A57 r0p0-r1p1: Supported, not security supported
Status, Cortex A77 r0p0-r1p0: Supported, not security supported
+ Status, Xen in AArch32 mode: Tech Preview
For the Cortex A57 r0p0 - r1p1, see Errata 832075.
For the Cortex A77 r0p0 - r1p0, see Errata 1508412.
--
2.25.1
next reply other threads:[~2024-02-29 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 12:13 Michal Orzel [this message]
2024-02-29 12:35 ` [PATCH] SUPPORT.md: clarify support of booting 32-bit Xen on ARMv8 Julien Grall
2024-02-29 12:37 ` Michal Orzel
2024-02-29 12:40 ` Julien Grall
2024-02-29 12:42 ` Michal Orzel
2024-02-29 21:07 ` Stefano Stabellini
2024-03-06 9:40 ` Julien Grall
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=20240229121352.11264-1-michal.orzel@amd.com \
--to=michal.orzel@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.