From: Marc Zyngier <maz@kernel.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 1/3] arm64: Use FEAT_HAFDBS to track dirty pages when available
Date: Fri, 13 Oct 2023 23:04:10 +0100 [thread overview]
Message-ID: <fac6ef1747ec318787f90a6d0c81163b@kernel.org> (raw)
In-Reply-To: <CAFOYHZC_Dveax85n0fLr5BFyZcLqsvUssn=J0oHyvN75bTaCUw@mail.gmail.com>
On 2023-10-13 03:40, Chris Packham wrote:
> Hi Marc, Paul,
>
> On Sat, Mar 18, 2023 at 5:23 AM Ying-Chun Liu (PaulLiu)
> <paul.liu@linaro.org> wrote:
>>
>> From: Marc Zyngier <maz@kernel.org>
>>
>> Some recent arm64 cores have a facility that allows the page
>> table walker to track the dirty state of a page. This makes it
>> really efficient to perform CMOs by VA as we only need to look
>> at dirty pages.
>>
>> Signed-off-by: Marc Zyngier <maz@kernel.org>
>> [ Paul: pick from the Android tree. Rebase to the upstream ]
>> Signed-off-by: Ying-Chun Liu (PaulLiu) <paul.liu@linaro.org>
>> Cc: Tom Rini <trini@konsulko.com>
>> Link:
>> https://android.googlesource.com/platform/external/u-boot/+/3c433724e6f830a6b2edd5ec3d4a504794887263
>
> I think this may have caused a regression for the Marvell AC5X
> board(s). I found that v2023.07 locked up at boot but v2023.01 was
> fine. The lockup seemed to be in the 'Net:' init probably just as the
> mvneta driver was being initialised.
>
> A git bisect led me to this change although for this specific change
> instead of the lockup I get a crash so maybe I'm actually hitting a
> different issue.
>
> Any thoughts as to why this may have caused problems?
Not really. What CPUs does this platform have? What is the offending
driver doing to trigger the issue? Can you provide some level of
tracing?
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2023-10-14 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:22 [PATCH 0/3] Use FEAT_HAFDBS to track dirty pages Ying-Chun Liu (PaulLiu)
2023-03-17 16:22 ` [PATCH 1/3] arm64: Use FEAT_HAFDBS to track dirty pages when available Ying-Chun Liu (PaulLiu)
2023-04-26 12:30 ` Tom Rini
2023-10-13 2:40 ` Chris Packham
2023-10-13 22:04 ` Marc Zyngier [this message]
2023-10-14 21:29 ` Chris Packham
2023-10-16 1:42 ` Chris Packham
2023-10-16 11:21 ` Marc Zyngier
2023-10-17 4:22 ` Chris Packham
2023-03-17 16:22 ` [PATCH 2/3] arm64: Use level-2 for largest block mappings when FEAT_HAFDBS is present Ying-Chun Liu (PaulLiu)
2023-04-26 12:30 ` Tom Rini
2023-03-17 16:22 ` [PATCH 3/3] armv8: enable HAFDBS for other ELx " Ying-Chun Liu (PaulLiu)
2023-04-26 12:30 ` Tom Rini
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=fac6ef1747ec318787f90a6d0c81163b@kernel.org \
--to=maz@kernel.org \
--cc=judge.packham@gmail.com \
--cc=paul.liu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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