From: Johannes Kirchmair <johannes.kirchmair@sigmatek.at>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Xenomai <xenomai@lists.linux.dev>,
Philippe Gerum <rpm@xenomai.org>,
Richard Weinberger <richard@nod.at>
Subject: RE: [RFC][PATCH] x86: dovetail: Permit to declare a trap handled
Date: Wed, 9 Nov 2022 07:31:35 +0000 [thread overview]
Message-ID: <VE1PR08MB4909620AE0E4EE0139B54276923E9@VE1PR08MB4909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <8929fce3-cbe6-79cf-d0a9-5e8399e3dec4@siemens.com>
Hello all,
I just recently found the time to test this patch in the context of our rt_signals.
As a matter of fact it works quite well for us.
So is there any intent/possibility to bring this upstream?
I also did some similar changes for arm64. As we also use imx8 boards.
If there is interest in those, I could post them.
Best regards
Johannes
> -----Original Message-----
> From: Jan Kiszka <jan.kiszka@siemens.com>
> Sent: Freitag, 8. Juli 2022 09:13
> To: Xenomai <xenomai@lists.linux.dev>; Philippe Gerum <rpm@xenomai.org>;
> Johannes Kirchmair <johannes.kirchmair@sigmatek.at>; Richard Weinberger
> <richard@nod.at>
> Subject: Re: [RFC][PATCH] x86: dovetail: Permit to declare a trap handled
>
> On 08.07.22 09:11, Jan Kiszka wrote:
> > From: Jan Kiszka <jan.kiszka@siemens.com>
> >
> > This allows to skip reporting a trap to Linux when the OOB handler
> > resolved it directly. The handler can signal this condition by returning
> > "true". This feature was present in I-pipe as well.
> >
> > By intention, not all spots of oob_trap_notify are enabled for this.
> > Debug traps are left out as well as asyncpf in kvm - no use cases from
> > OOB-perspective.
> >
> > NOTE: breaks unprepared users, breaks non-x86.
> >
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> >
> > I'm happy to add non-x86 support as well if the direction is fine.
> >
> > And if we introduce that to dovetail, we will have to add some kernel
> > version checks to Xenomai so that it does the right thing with the right
> > dovetail versions. Feature flags are out of fashion there as far as I
> > understood.
> >
>
> And I forgot to write that this if for v5.19-dovetail-rebase. I have a
> 5.10 version locally as well, the one we use in a downstream deployment
> for some months now.
>
> Jan
>
> --
> Siemens AG, Technology
> Competence Center Embedded Linux
next prev parent reply other threads:[~2022-11-09 7:31 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 [this message]
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
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=VE1PR08MB4909620AE0E4EE0139B54276923E9@VE1PR08MB4909.eurprd08.prod.outlook.com \
--to=johannes.kirchmair@sigmatek.at \
--cc=jan.kiszka@siemens.com \
--cc=richard@nod.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).