From: Richard Weinberger <richard@sigma-star.at>
To: Nikolaus Funk <nikolaus.funk@sigmatek.at>,
xenomai@lists.linux.dev, Jan Kiszka <jan.kiszka@siemens.com>
Cc: Richard Weinberger <richard@nod.at>
Subject: Re: [RFC PATCH 0/6] Xenomai: Real-time Exception Handling
Date: Tue, 08 Apr 2025 20:39:57 +0200 [thread overview]
Message-ID: <6934535.sGJI6kyIVQ@anvil> (raw)
In-Reply-To: <879ad6e6-3f38-4f22-aa74-fa3862d85cb5@siemens.com>
On Dienstag, 8. April 2025 19:32 Jan Kiszka wrote:
> > real-time. A notable example is a page fault, determining whether
> > SIGSEGV is appropriate requires deep traversal into the memory
> > management code.
>
> ...on arm and arm64. It worked fairly well for x86. This is indeed a
> very prominent exception that people may expect behind this feature. And
> it is also a use case we have with our (x86-only) deployment.
True that.
I think the set of supported exceptions should be architecture specific
anyways. And we need to state that it is best effort.
>
> >
> > Patches 1, 2, 3, and 4 implement the Xenomai-side changes for this
> > feature. Dovetail will receive a separate patch set. Patches 5 and 6
> > introduce tests.
> >
> > It is important to note that this is not a fully-fledged signal
> > implementation. The only supported use case is delivering exceptions
> > as signals to the affected thread.
> > There is no support for sending signals or handling block/ignore masks.
> > The only user visible API so far is cobalt_rt_signal().
> > It takes a signal number (SIGILL or SIGFPE so far) and a handler
> > function with the signature fn(int, siginfo_t *, void *).
>
> Did you intentionally left out the oldact parameter of sigaction?
Not really. Adding this should be trivial.
Maybe my subconsciousness tried to make it less look like POSIX
real time signals. ;-)
>
> >
> > TODO:
> > - Better naming, IMHO "signal" is the wrong term and will confuse users.
> > Especially since POSIX real-time signals are something different.
> > Maybe "umex" for "user mode exception handling"?
>
> Just "exception" might be enough and clearer. OTOH, we are reusing a lot
> of sigaction and siginfo...
That's the problem. It kinda looks like signals but isn't.
>
> > - Document new APIs
> > - Improve tests
> > - Carefully select more exceptions
>
> Yeah, that is the challenge.
>
> And:
>
> - align with EVL / Xenomai 4 to ensure compatible features
Agreed.
The dovetail side is rather small. We could also integrate the signal frame
helper functions into Xenomai.
Thanks,
//richard
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT UID/VAT Nr:
ATU 66964118 | FN: 374287y
next prev parent reply other threads:[~2025-04-08 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 12:28 [RFC PATCH 0/6] Xenomai: Real-time Exception Handling Nikolaus Funk
2025-04-08 12:28 ` [PATCH 1/6] cobalt/x86: Add architecture specific signal code Nikolaus Funk
2025-04-08 12:28 ` [PATCH 2/6] cobalt/arm64: " Nikolaus Funk
2025-04-08 12:28 ` [PATCH 3/6] cobalt/arm: " Nikolaus Funk
2025-04-08 12:28 ` [PATCH 4/6] cobalt: Add signal core code Nikolaus Funk
2025-04-08 12:28 ` [PATCH 5/6] testsuite: smokey: Add testcases for signals Nikolaus Funk
2025-04-08 12:28 ` [PATCH 6/6] utils: Add rt_signal_hist Nikolaus Funk
2025-04-08 17:32 ` [RFC PATCH 0/6] Xenomai: Real-time Exception Handling Jan Kiszka
2025-04-08 18:39 ` Richard Weinberger [this message]
2025-04-10 9:45 ` 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=6934535.sGJI6kyIVQ@anvil \
--to=richard@sigma-star.at \
--cc=jan.kiszka@siemens.com \
--cc=nikolaus.funk@sigmatek.at \
--cc=richard@nod.at \
--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.