From: Tim Sander <tim@krieglstein.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Florian Paul Schmidt <mista.tapas@gmx.net>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Raspberry Pi 5 and PREEMPT_RT (6.13.0-rc3)
Date: Tue, 28 Jan 2025 13:30:59 +0100 [thread overview]
Message-ID: <4625492.LvFx2qVVIh@ripper> (raw)
In-Reply-To: <6b290601-7112-410b-9a85-bde02f62d7c3@gmx.net>
Hi
Just my 2 ct.
Am Mittwoch, 8. Januar 2025, 10:48:56 CET schrieb Florian Paul Schmidt:
> Hi!
>
> On 1/7/2025 3:39 PM, Sebastian Andrzej Siewior wrote:
> > On 2024-12-20 14:18:43 [+0100], Florian Paul Schmidt wrote:
> [...]
>
> > The backtrace appears long but everything up to folios_put_refs()
> > appears preemtible. Then there is the interrupt handler. This looks
> > okay.
>
> That was my impression as well. Nothing really surprising (at least for
> my limited knowledge in these matters.)
>
> > Based on this trace, I don't see a section which disables preemption/
> > interrupts and be the reason for the interrupt happening.
> >
> > One thing that could delay your doing are small caches.
> > Then there is looking within the system: An inaccurate/ low resolution
> > clocksource and/ or timer device.
It could also be the TLB infrastructure. I found that these events can also be
very time consuming, probably combined with memory contention?
I think this might be traced with performance counters but i never looked into
this further than musing about the possibility.
Best regards
Tim
prev parent reply other threads:[~2025-01-28 12:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:18 Raspberry Pi 5 and PREEMPT_RT (6.13.0-rc3) Florian Paul Schmidt
2024-12-20 14:05 ` John Ogness
2024-12-20 15:57 ` Florian Paul Schmidt
2024-12-22 10:32 ` Leon Woestenberg
2025-01-08 9:42 ` Florian Paul Schmidt
2025-01-12 15:14 ` Florian Paul Schmidt
2025-01-12 21:30 ` John Ogness
2025-01-13 9:15 ` Florian Paul Schmidt
2025-01-13 10:28 ` Florian Paul Schmidt
2025-01-13 11:09 ` John Ogness
2025-01-13 12:56 ` Florian Paul Schmidt
2025-01-14 10:28 ` Mike Galbraith
2025-02-14 8:31 ` Florian Paul Schmidt
2025-02-14 9:05 ` Mike Galbraith
2025-02-14 12:40 ` gene heskett
2025-02-14 12:06 ` Gabriele Monaco
2025-01-09 8:39 ` Florian Paul Schmidt
2025-01-07 14:39 ` Sebastian Andrzej Siewior
2025-01-08 9:48 ` Florian Paul Schmidt
2025-01-28 12:30 ` Tim Sander [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=4625492.LvFx2qVVIh@ripper \
--to=tim@krieglstein.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=mista.tapas@gmx.net \
/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