From: Richard Weinberger <richard.weinberger@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Richard Weinberger <richard@sigma-star.at>,
Philippe Gerum <rpm@xenomai.org>,
Xenomai <xenomai@lists.linux.dev>
Subject: Re: [RFC][PATCH] x86: dovetail: Permit to declare a trap handled
Date: Mon, 12 Feb 2024 16:14:28 +0100 [thread overview]
Message-ID: <CAFLxGvytJP_ibg0ex4zgyahaxNJH2b_M=Nu3ZBWtrm9neRoW9w@mail.gmail.com> (raw)
In-Reply-To: <3ca2aaf3-f47e-4fbf-8d46-b5da9542bc3c@siemens.com>
On Mon, Feb 12, 2024 at 4:12 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >> 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?
>
> Yes, I do have some first hacks here as well. ARM and ARM64 is not yet
> ready for this, unfortunately.
Can you please share your hacks?
What is missing? I'll happily continue your work.
--
Thanks,
//richard
next prev parent reply other threads:[~2024-02-12 15:14 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
2024-02-12 15:12 ` Jan Kiszka
2024-02-12 15:14 ` Richard Weinberger [this message]
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='CAFLxGvytJP_ibg0ex4zgyahaxNJH2b_M=Nu3ZBWtrm9neRoW9w@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=richard@sigma-star.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).