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: [PATCH v2 6/6] aarch64: Start Xen on Armv8-R at EL2
Date: Tue, 23 Jul 2024 12:35:36 +0000 [thread overview]
Message-ID: <968CB3CD-F56F-491C-940D-6571F93448EC@arm.com> (raw)
In-Reply-To: <Zp-hqtjy1fgLb38H@J2N7QTR9R3>
Hi Mark,
> On 23 Jul 2024, at 13:27, Mark Rutland <mark.rutland@arm.com> wrote:
>
> On Tue, Jul 16, 2024 at 03:29:06PM +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.
>>
>> Signed-off-by: Luca Fancellu <luca.fancellu@arm.com>
>
> Just to check, this requires using spin-table, right?
>
> I don't expect there to be interworking between the boot-wrapper and
> Xen.
Yes Xen on Armv8-R AArch64 requires spin-table.
Cheers,
Luca
prev parent reply other threads:[~2024-07-23 12:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 14:29 [PATCH v2 0/6] Add Armv8-R AArch64 support Luca Fancellu
2024-07-16 14:29 ` [PATCH v2 1/6] aarch64: Rename labels and prepare for lower EL booting Luca Fancellu
2024-07-16 14:29 ` [PATCH v2 2/6] aarch64: Prepare " Luca Fancellu
2024-07-16 14:29 ` [PATCH v2 3/6] aarch64: Remove TSCXT bit set from SCTLR_EL2_RESET Luca Fancellu
2024-07-19 10:05 ` Mark Rutland
2024-07-16 14:29 ` [PATCH v2 4/6] aarch64: Introduce EL2 boot code for Armv8-R AArch64 Luca Fancellu
2024-07-29 15:01 ` Mark Rutland
2024-07-29 15:27 ` Luca Fancellu
2024-07-29 16:14 ` Mark Rutland
2024-07-16 14:29 ` [PATCH v2 5/6] aarch64: Support PSCI " Luca Fancellu
2024-07-29 16:09 ` Mark Rutland
2024-07-30 11:31 ` Luca Fancellu
2024-07-30 12:55 ` Mark Rutland
2024-07-16 14:29 ` [PATCH v2 6/6] aarch64: Start Xen on Armv8-R at EL2 Luca Fancellu
2024-07-23 12:27 ` Mark Rutland
2024-07-23 12:35 ` Luca Fancellu [this message]
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=968CB3CD-F56F-491C-940D-6571F93448EC@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