From: Philippe Gerum <rpm@xenomai.org>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: Dovetail 5.10 - Xenomai huge page support
Date: Thu, 20 Jan 2022 09:32:35 +0100 [thread overview]
Message-ID: <87sftig62e.fsf@xenomai.org> (raw)
In-Reply-To: <745119239ef0a715f703f8315befc79ee34d0511.camel@siemens.com>
"Bezdeka, Florian" <florian.bezdeka@siemens.com> writes:
> On Wed, 2022-01-19 at 13:35 +0000, Bezdeka, Florian via Xenomai wrote:
>> Hi all,
>>
>> after migrating from 4.19-ipipe to 5.10-dovetail internal users are
>> reporting that they receive sporadic SIGXCPUs. The reported reason is
>> "page_fault_user".
>>
>> After disabling the huge page support in 5.10 the issue vanished. Tests
>> are still running, but we are optimistic that we found the root cause.
>>
>> Are there any known limitations to the huge page support in Xenomai /
>> Dovetail? My understanding is that huge pages are supported by Xenomai,
>> so any ideas where to look at?
>
> [1] is part of the 5.15-rebased dovetail branch but not part of the
> 5.10-rebase branch and mentions huge page handling. Could that be
> related? Maybe this patch is not 5.15 specific?
>
It is not 5.15 specific. The same logic would apply to 5.10.
> [1] https://source.denx.de/Xenomai/linux-dovetail/-/commit/b0a4f4c3891949d079aa3d65f2a56428a67e580c
>
>>
>> Best regards,
>> Florian
--
Philippe.
next prev parent reply other threads:[~2022-01-20 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 13:35 Dovetail 5.10 - Xenomai huge page support Bezdeka, Florian
2022-01-19 13:49 ` Bezdeka, Florian
2022-01-20 8:32 ` Philippe Gerum [this message]
2022-01-20 9:15 ` Bezdeka, Florian
2022-01-25 16:48 ` Jan Kiszka
2022-01-25 17:43 ` Philippe Gerum
2022-01-20 8:30 ` Philippe Gerum
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=87sftig62e.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.org \
/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.