From: Marc Zyngier <maz@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
<lkft-triage@lists.linaro.org>,
Linux Regressions <regressions@lists.linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20240219: arm64: boot failed - gic_of_init
Date: Mon, 19 Feb 2024 15:27:52 +0000 [thread overview]
Message-ID: <86a5nw4gp3.wl-maz@kernel.org> (raw)
In-Reply-To: <a7d8e529-9a44-3f88-50ef-d87b80515c36@huawei.com>
On Mon, 19 Feb 2024 14:46:46 +0000,
Zenghui Yu <yuzenghui@huawei.com> wrote:
>
> On 2024/2/19 19:32, Marc Zyngier wrote:
> > For what it is worth, I've just tested both defconfig and my own
> > configuration with both 4k (kvmtool, QEMU+KVM and on SynQuacer) and
> > 16k (kvmtool), without any obvious problem.
>
> I had a quick test on top of next-20240219 with defconfig. I can
> reproduce it with QEMU parameter '-cpu max -accel tcg', but things are
> fine with '-cpu max,lpa2=off -accel tcg'.
>
> Bisection shows that the problem happens when we start putting the
> latest arm64 and kvmarm changes together. The following hack fixes the
> problem for me (but I **only** write it for kernel built with defconfig
> with ARM64_4K_PAGES=y atm).
>
> I can investigate it further tomorrow (as it's too late now ;-) ). Or
> maybe Marc or Catalin can help fix it with a proper approach.
>
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index 4f7662008ede..babdc3f4721b 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -2798,6 +2798,7 @@ static const struct arm64_cpu_capabilities
> arm64_features[] = {
> | .sign = FTR_SIGNED,
> | .field_pos = ID_AA64MMFR0_EL1_TGRAN4_SHIFT,
> | .min_field_value = ID_AA64MMFR0_EL1_TGRAN4_52_BIT,
> |+ .max_field_value = BIT(ID_AA64MMFR0_EL1_TGRAN4_WIDTH - 1) - 1,
> | #else
> | .sign = FTR_UNSIGNED,
> | .field_pos = ID_AA64MMFR0_EL1_TGRAN16_SHIFT,
I've posted my take on this at [1], which hopefully matches what you
were aiming at.
Thanks,
M.
[1] https://lore.kernel.org/all/86bk8c4gyh.wl-maz@kernel.org/
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
<lkft-triage@lists.linaro.org>,
Linux Regressions <regressions@lists.linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20240219: arm64: boot failed - gic_of_init
Date: Mon, 19 Feb 2024 15:27:52 +0000 [thread overview]
Message-ID: <86a5nw4gp3.wl-maz@kernel.org> (raw)
In-Reply-To: <a7d8e529-9a44-3f88-50ef-d87b80515c36@huawei.com>
On Mon, 19 Feb 2024 14:46:46 +0000,
Zenghui Yu <yuzenghui@huawei.com> wrote:
>
> On 2024/2/19 19:32, Marc Zyngier wrote:
> > For what it is worth, I've just tested both defconfig and my own
> > configuration with both 4k (kvmtool, QEMU+KVM and on SynQuacer) and
> > 16k (kvmtool), without any obvious problem.
>
> I had a quick test on top of next-20240219 with defconfig. I can
> reproduce it with QEMU parameter '-cpu max -accel tcg', but things are
> fine with '-cpu max,lpa2=off -accel tcg'.
>
> Bisection shows that the problem happens when we start putting the
> latest arm64 and kvmarm changes together. The following hack fixes the
> problem for me (but I **only** write it for kernel built with defconfig
> with ARM64_4K_PAGES=y atm).
>
> I can investigate it further tomorrow (as it's too late now ;-) ). Or
> maybe Marc or Catalin can help fix it with a proper approach.
>
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index 4f7662008ede..babdc3f4721b 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -2798,6 +2798,7 @@ static const struct arm64_cpu_capabilities
> arm64_features[] = {
> | .sign = FTR_SIGNED,
> | .field_pos = ID_AA64MMFR0_EL1_TGRAN4_SHIFT,
> | .min_field_value = ID_AA64MMFR0_EL1_TGRAN4_52_BIT,
> |+ .max_field_value = BIT(ID_AA64MMFR0_EL1_TGRAN4_WIDTH - 1) - 1,
> | #else
> | .sign = FTR_UNSIGNED,
> | .field_pos = ID_AA64MMFR0_EL1_TGRAN16_SHIFT,
I've posted my take on this at [1], which hopefully matches what you
were aiming at.
Thanks,
M.
[1] https://lore.kernel.org/all/86bk8c4gyh.wl-maz@kernel.org/
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-19 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:42 next-20240219: arm64: boot failed - gic_of_init Naresh Kamboju
2024-02-19 9:42 ` Naresh Kamboju
2024-02-19 9:48 ` Marc Zyngier
2024-02-19 9:48 ` Marc Zyngier
2024-02-19 11:32 ` Marc Zyngier
2024-02-19 11:32 ` Marc Zyngier
2024-02-19 14:46 ` Zenghui Yu
2024-02-19 14:46 ` Zenghui Yu
2024-02-19 15:02 ` Marc Zyngier
2024-02-19 15:02 ` Marc Zyngier
2024-02-19 15:27 ` Marc Zyngier [this message]
2024-02-19 15:27 ` Marc Zyngier
2024-02-20 2:26 ` Zenghui Yu
2024-02-20 2:26 ` Zenghui Yu
2024-02-20 10:30 ` Naresh Kamboju
2024-02-20 10:30 ` Naresh Kamboju
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=86a5nw4gp3.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=yuzenghui@huawei.com \
/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.