public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
	u-boot@lists.denx.de, "Pierre-Clément Tosi" <ptosi@google.com>,
	"Tom Rini" <trini@konsulko.com>,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>
Subject: Re: [PATCH 1/2] arm64: Reduce add_map() complexity
Date: Sat, 09 Mar 2024 12:39:21 +0000	[thread overview]
Message-ID: <87zfv7pojq.wl-maz@kernel.org> (raw)
In-Reply-To: <CAOMZO5DBzEcga0-QGBBP3twT6imLuCv0cD6EYLOTwGN47wTxsA@mail.gmail.com>

On Sat, 09 Mar 2024 12:29:10 +0000,
Fabio Estevam <festevam@gmail.com> wrote:
> 
> Hi Marc,
> 
> On Sat, Mar 9, 2024 at 6:53 AM Marc Zyngier <maz@kernel.org> wrote:
> 
> > It would be good to narrow down which access is generating this. It is
> > an asynchronous error, so the code above won't help.
> >
> > Alternatively, and if you are sure that this is due to this change,
> > dumping the page tables and comparing them before and after would
> > help.
> 
> Yes, I am sure the error is due to this change. It is 100% reproducible.

Can you figure out what memory access is triggering it? Even at
narrowing it to the subsystem level would be a good indication.

> I am not familiar with this part of the code, so I would appreciate
> it if you could tell me how to dump the page tables so I can compare
> them before and after.

You could just dump the entries as they are written. The order may not
be the same, but for a given VA you should observe the same entries
being written.

My hunch is that the new code is a lot more picky about the alignment
of things, and that could result in something being similarly
unaligned. But without access to the platform nor an idea of what gets
mapped, it's a bit hard to have a clue.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2024-03-09 12:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 13:38 [PATCH 0/2] Reduce the complexity of add_map() and count_required_pts() Ying-Chun Liu (PaulLiu)
2023-02-14 13:38 ` [PATCH 1/2] arm64: Reduce add_map() complexity Ying-Chun Liu (PaulLiu)
2023-03-07 17:52   ` Tom Rini
2023-08-01  8:53   ` Oliver Graute
2023-08-01 12:09     ` Oliver Graute
2023-08-01 17:31     ` Marc Zyngier
2024-03-08 20:22   ` Fabio Estevam
2024-03-09  9:52     ` Marc Zyngier
2024-03-09 12:29       ` Fabio Estevam
2024-03-09 12:39         ` Marc Zyngier [this message]
2024-03-09 14:36           ` Fabio Estevam
2024-03-15 11:56             ` Fabio Estevam
2024-03-15 15:13               ` Pierre-Clément Tosi
2024-03-18 13:31                 ` Fabio Estevam
2024-03-18 13:50                   ` Fabio Estevam
2024-03-18 19:59                   ` Pierre-Clément Tosi
2024-03-18 20:09                     ` Fabio Estevam
2023-02-14 13:38 ` [PATCH 2/2] arm64: Reduce PT size estimation complexity Ying-Chun Liu (PaulLiu)
2023-03-07 17:52   ` 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=87zfv7pojq.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=paul.liu@linaro.org \
    --cc=ptosi@google.com \
    --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