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>,
Johannes Kirchmair <johannes.kirchmair@sigmatek.at>,
Lorenz Kofler <lorenz@sigma-star.at>
Subject: Re: [PATCH 3/5] arm64: dovetail: Allow early return from traps
Date: Wed, 09 Apr 2025 11:47:43 +0200 [thread overview]
Message-ID: <3083486.KX7oQKdZxJ@anvil> (raw)
In-Reply-To: <a28841a2-cb96-4356-93c1-ba08eb954210@siemens.com>
On Dienstag, 8. April 2025 19:06 Jan Kiszka wrote:
> On 08.04.25 14:34, Nikolaus Funk wrote:
> > From: Richard Weinberger <richard@nod.at>
> >
> > Like on the x86 side, allow early return such that
> > handling the exception on the Linux can get avoided.
> >
>
> Which traps can be caught and fully handled in oob this way? From my
> past experiments, that list was not very long - and when I look at your
> Xenomai 3 changes, it still isn't. What was particularly hard: DABT and
> memory access faults.
The list is indeed short.
So far ARM64_TRAP_UNDI/BTI and ALIGN look good.
> Point is that we need to have some kind of consistency, between the
> archs and between the reporting information (Linux vs. OOB signals). Or
> we extensively need to document where all we are deviating (and ideally
> why).
I'd vote for the latter.
Plus improving the rt_signal_hist test such that others can
test whether some exception handling is good enough or nor.
So, I suggest exposing more exception but mark/document the known good
ones explicitly.
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-09 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 12:34 [RFC PATCH 0/5] Dovetail: Real-time Exception Handling Nikolaus Funk
2025-04-08 12:34 ` [PATCH 1/5] arm: dovetail: Fix user mode UND exception handling Nikolaus Funk
2025-04-08 12:34 ` [PATCH 2/5] x86: dovetail: Helper functions for signal frame setup and restore Nikolaus Funk
2025-04-08 12:34 ` [PATCH 3/5] arm64: dovetail: Allow early return from traps Nikolaus Funk
2025-04-08 12:58 ` Florian Bezdeka
2025-04-08 13:24 ` Richard Weinberger
2025-04-08 17:06 ` Jan Kiszka
2025-04-09 9:47 ` Richard Weinberger [this message]
2025-04-09 14:25 ` Jan Kiszka
2025-04-08 12:34 ` [PATCH 4/5] arm64: dovetail: Helper functions for signal frame setup and restore Nikolaus Funk
2025-04-08 13:05 ` Florian Bezdeka
2025-04-08 13:16 ` Richard Weinberger
2025-04-08 12:34 ` [PATCH 5/5] arm: " Nikolaus Funk
2025-04-08 13:12 ` Florian Bezdeka
2025-04-08 13:18 ` Richard Weinberger
2025-04-08 16:58 ` [RFC PATCH 0/5] Dovetail: Real-time Exception Handling Jan Kiszka
2025-04-08 17:55 ` Richard Weinberger
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=3083486.KX7oQKdZxJ@anvil \
--to=richard@sigma-star.at \
--cc=jan.kiszka@siemens.com \
--cc=johannes.kirchmair@sigmatek.at \
--cc=lorenz@sigma-star.at \
--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.