From: Richard Weinberger <richard@sigma-star.at>
To: Johannes Kirchmair <johannes.kirchmair@sigmatek.at>,
Philippe Gerum <rpm@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@lists.linux.dev>
Subject: Re: [RFC][PATCH] x86: dovetail: Permit to declare a trap handled
Date: Mon, 12 Feb 2024 16:04:12 +0100 [thread overview]
Message-ID: <5809272.1B3tZ46Xf9@somecomputer> (raw)
In-Reply-To: <874jv7rxb2.fsf@xenomai.org>
Hi!
Sorry for exhuming this old mail thread.
Am Donnerstag, 10. November 2022, 10:00:33 CET schrieb Philippe Gerum:
> >> >>> I also did some similar changes for arm64. As we also use imx8 boards.
> >> >>> If there is interest in those, I could post them.
> >> >>
> >> >> Yes, please share. Then we can continue with proposing it for the latest
> >> >> dovetail port (6.1 now).
> >> >>
> >> >
> >> > There is a slightly different approach which expresses the intent of
> >> > that notification hook Dovetail-wise:
> >> >
> >> > - if the real-time core switches in-band upon notification, then the
> >> > in-band kernel code may assume that all regular fixups need to be
> >> > applied next. This is the common case for most traps.
> >> >
> >> > - if the real-time core stays on the out-of-band stage upon
> >> > notification, then the in-band kernel code should assume that all
> >> > required fixups were done from that stage already, returning asap from
> >> > the outer trap handler.
> >> >
> >> > This gives the same flexibility than by expecting the hook to return a
> >> > continuation status, but makes sure that regular fixups cannot be
> >> > bypassed when/if switching to in-band mode is required to handle the
> >> > trap. Rationale: the regular in-band trap handlers know better about the
> >> > way to deal with those events from in-band context.
> >> >
> >
> > I like that idea because as I was looking at the arm code, I was not sure what would happen if we are out of band but
> > indicate that the kernel should handle the exception. With your idea that’s not possible.
> >
> > Will have a look at my arm64 patch and try to adapt it.
> >
>
> Ok, so since the idea is generally agreed, I'll push the x86 and arm
> support for this in a couple of days.
Currently, I'm looking into implementing Johannes's RT-Signals for ARM64,
but from what I see on the dovetail side, only x86 has gained support to declare traps handled.
At least on x86, I see that a trap is considered handled if no switch to in-band has occurred.
Did I miss something?
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:[~2024-02-12 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:11 [RFC][PATCH] x86: dovetail: Permit to declare a trap handled Jan Kiszka
2022-07-08 7:12 ` Jan Kiszka
2022-11-09 7:31 ` Johannes Kirchmair
2022-11-09 9:28 ` Jan Kiszka
2022-11-09 10:06 ` Philippe Gerum
2022-11-09 10:38 ` Jan Kiszka
2022-11-09 11:42 ` Johannes Kirchmair
2022-11-10 9:00 ` Philippe Gerum
2024-02-12 15:04 ` Richard Weinberger [this message]
2024-02-12 15:12 ` Jan Kiszka
2024-02-12 15:14 ` Richard Weinberger
2024-02-12 16:12 ` Jan Kiszka
2024-03-28 7:28 ` Richard Weinberger
2024-04-08 11:59 ` Jan Kiszka
2022-11-09 7:36 ` Johannes Kirchmair
2022-11-09 9:29 ` Jan Kiszka
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=5809272.1B3tZ46Xf9@somecomputer \
--to=richard@sigma-star.at \
--cc=jan.kiszka@siemens.com \
--cc=johannes.kirchmair@sigmatek.at \
--cc=rpm@xenomai.org \
--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.