From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Tobias Schaffner <tobias.schaffner@siemens.com>,
Xenomai <xenomai@lists.linux.dev>,
Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: Possible Xenomai 3 latency regression on arm64
Date: Mon, 22 Jun 2026 10:53:59 +0200 [thread overview]
Message-ID: <871pdzez14.fsf@xenomai.org> (raw)
In-Reply-To: <6fab68d3def30cfc168e81fc9a4e7334c18ec035.camel@siemens.com> (Florian Bezdeka's message of "Mon, 22 Jun 2026 09:39:16 +0200")
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> On Mon, 2026-06-22 at 09:13 +0200, Philippe Gerum wrote:
>> Philippe Gerum <rpm@xenomai.org> writes:
>>
>> > Jan Kiszka <jan.kiszka@siemens.com> writes:
>> >
>> > > On 15.06.26 09:35, Philippe Gerum wrote:
>> > > > Jan Kiszka <jan.kiszka@siemens.com> writes:
>> > > >
>> > > > > Hi all,
>> > > > >
>> > > > > it seems we got some >10% worst-case latency increase over the last
>> > > > > month with Xenomai head and 6.12 - that is at least the setup we use in
>> > > > > our long-running weekly test.
>> > > > >
>> > > > > Tonight, the RPi4 test triggered by exceeding the configured limit of
>> > > > > 150 µs [1]. About half a year ago, we were in 130 µs range with it [2].
>> > > > > x86 and beaglebone are apparently not seeing this change.
>> > > > >
>> > > >
>> > > > My rpi4 fried. Is the issue visible with x4 as well?
>> > > >
>> > >
>> > > We do not have long-running latency tests for x4 yet, do we, Tobias?
>> > >
>> >
>> > Ok, I can try this on an odroid c4. Did anyone succeeded in booting a
>> > mainline kernel on pi5? Last time I checked, root-over-nfs was not
>> > possible yet.
>>
>> A follow up on the latency issue. I did notice a regression in the
>> latency figures with v4 too, specifically on arm64. The issue was
>> introduced in v6.12.85-cip22-dovetail3-rebase, where vDSO support for
>> oob callers was unexpectedly disabled due to applying 682c4aa14fe6. That
>> change is correct starting from v6.18.y, but should not have been
>> applied to v6.12.y. The bug caused a ~12% increase in the worst-case
>> latency figures on odroid c4.
>>
>> With that change reverted, I'm back to normal on c4 with
>> v6.12.90-cip24-dovetail2-rebase. A couple of additional fixes to the
>> generic lib/vdso support went in as well, but those have no effect on
>> latency.
>>
>> All dovetail and v4/evl branches have been updated accordingly.
>
> All those changes are not yet part of the 7.1 branches (which have been
> recently rebased to the first 7.1 release). Will you (Philippe) take
> care of integrating that or should I pick it?
If you already merged the latest changes from 7.0 into 7.1 on the fly,
please pick them, otherwise I'll do it.
--
Philippe.
next prev parent reply other threads:[~2026-06-22 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 5:46 Possible Xenomai 3 latency regression on arm64 Jan Kiszka
2026-06-15 7:35 ` Philippe Gerum
2026-06-15 8:33 ` Jan Kiszka
2026-06-15 8:52 ` Philippe Gerum
2026-06-15 10:39 ` Tobias Schaffner
2026-06-22 7:13 ` Philippe Gerum
2026-06-22 7:39 ` Florian Bezdeka
2026-06-22 8:53 ` Philippe Gerum [this message]
2026-06-15 10:28 ` Tobias Schaffner
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=871pdzez14.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.