From: Jaxson Han <Jaxson.Han@arm.com>
To: Andre Przywara <Andre.Przywara@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Wei Chen <Wei.Chen@arm.com>
Subject: RE: [boot-wrapper PATCH v3 0/8] Add Armv8-R AArch64 support
Date: Tue, 13 Jul 2021 02:18:13 +0000 [thread overview]
Message-ID: <AS8PR08MB61172DA13453096B16935DF883149@AS8PR08MB6117.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20210617125738.31f01418@slackpad.fritz.box>
Hi Mark and Andre,
I hope you are doing well. :)
May I ask about the situation of these patches and what else I can do to
improve them if needed?
Cheers,
Jaxson
> -----Original Message-----
> From: Andre Przywara <andre.przywara@arm.com>
> Sent: Thursday, June 17, 2021 7:58 PM
> To: Mark Rutland <Mark.Rutland@arm.com>
> Cc: Jaxson Han <Jaxson.Han@arm.com>; linux-arm-
> kernel@lists.infradead.org; Wei Chen <Wei.Chen@arm.com>
> Subject: Re: [boot-wrapper PATCH v3 0/8] Add Armv8-R AArch64 support
>
> On Tue, 25 May 2021 14:25:01 +0800
> Jaxson Han <jaxson.han@arm.com> wrote:
>
> Hi Mark,
>
> > Currently, we cannot boot Linux with boot-wrapper on Armv8-R AArch64:
> > 1. The Armv8-R AArch64 profile does not support the EL3.
> > 2. The Armv8-R AArch64 EL2 only supports a PMSA, which Linux does not
> > support. So it's necessary to drop into EL1 before entering the kernel.
> > 3. There is no EL2 booting code for Armv8-R AArch64 and no
> > configuration for dropping to EL1 in boot-wrapper.
> >
> > These patches enable boot-wrapper booting Linux with Armv8-R AArch64:
> > Patch 1 allows boot-wrapper to boot on more platforms.
> > Patch 2 renames some labels as preparations for booting from lower EL.
> > Patch 3 remove the redundant setup_stack.
> > Patch 4-5 does some preparations for lower EL booting.
> > Patch 6 prepares for GICv3 initialization with EL2.
> > Patch 7 adds necessary EL2 registers.
> > Patch 8 adds auto-detection for Armv8-R AArch64 to drop into EL1
> > before entering the kernel.
>
> So I reviewed the whole series (replies with the missing tags for 2/8 and 8/8
> are on the list), and am now happy with it.
> I also tested this for regressions with various v8-A models. I had some issues
> with the SMMU on RevC models, but this was also with boot-wrapper master
> and is unrelated to this series (as the kernel starts booting).
>
> So from my point of view this is good to go. Please let us know if you need
> more information or how we can help with anything to get this merged.
>
> Cheers,
> Andre
>
> > Refs: Arm Architecture Reference Manual Supplement - Armv8, for
> > Armv8-R AArch64 architecture profile.
> > [https://developer.arm.com/documentation/ddi0600/latest/]
> >
> > ---
> > v2 -> v3:
> > 1. Refine Patch 1 and move relevant changes into Patch 5 and 8.
> > 2. Refine Patch 8, more detailed comments and guarantees that those
> > CPUID fields never lose features when the value in a field increases.
> >
> > Jaxson Han (8):
> > Decouple V2M_SYS config by auto-detect dtb node
> > aarch64: Rename labels and prepare for lower EL booting
> > aarch64: Remove the redundant setup_stack
> > aarch64: Prepare for EL1 booting
> > aarch64: Prepare for lower EL booting
> > gic-v3: Prepare for gicv3 with EL2
> > aarch64: Prepare for booting with EL2
> > aarch64: Introduce EL2 boot code for Armv8-R AArch64
> >
> > Makefile.am | 4 +-
> > arch/aarch32/include/asm/gic-v3.h | 7 ++
> > arch/aarch64/boot.S | 151 +++++++++++++++++++++++++++---
> > arch/aarch64/include/asm/cpu.h | 3 +
> > arch/aarch64/include/asm/gic-v3.h | 38 +++++++-
> > arch/aarch64/psci.S | 13 +--
> > arch/aarch64/spin.S | 8 +-
> > arch/aarch64/utils.S | 10 +-
> > gic-v3.c | 2 +-
> > platform.c | 4 +
> > 10 files changed, 208 insertions(+), 32 deletions(-)
> >
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-07-13 2:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 6:25 [boot-wrapper PATCH v3 0/8] Add Armv8-R AArch64 support Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 1/8] Decouple V2M_SYS config by auto-detect dtb node Jaxson Han
2021-07-22 10:42 ` Mark Rutland
2021-05-25 6:25 ` [boot-wrapper PATCH v3 2/8] aarch64: Rename labels and prepare for lower EL booting Jaxson Han
2021-05-25 10:34 ` Andre Przywara
2021-07-23 16:48 ` Mark Rutland
2021-07-26 5:33 ` Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 3/8] aarch64: Remove the redundant setup_stack Jaxson Han
2021-07-22 10:41 ` Mark Rutland
2021-05-25 6:25 ` [boot-wrapper PATCH v3 4/8] aarch64: Prepare for EL1 booting Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 5/8] aarch64: Prepare for lower EL booting Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 6/8] gic-v3: Prepare for gicv3 with EL2 Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 7/8] aarch64: Prepare for booting " Jaxson Han
2021-05-25 6:25 ` [boot-wrapper PATCH v3 8/8] aarch64: Introduce EL2 boot code for Armv8-R AArch64 Jaxson Han
2021-05-25 10:38 ` Andre Przywara
2021-06-17 11:57 ` [boot-wrapper PATCH v3 0/8] Add Armv8-R AArch64 support Andre Przywara
2021-07-13 2:18 ` Jaxson Han [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=AS8PR08MB61172DA13453096B16935DF883149@AS8PR08MB6117.eurprd08.prod.outlook.com \
--to=jaxson.han@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Wei.Chen@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;
as well as URLs for NNTP newsgroup(s).