From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Johannes Kirchmair <johannes.kirchmair@sigmatek.at>,
"xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/3] [POC] test implementaion of rt-signals
Date: Mon, 11 Sep 2023 10:41:41 +0200 [thread overview]
Message-ID: <7212c5ca53968beeee4753065fbbb700e1ccdbd6.camel@siemens.com> (raw)
In-Reply-To: <VE1PR08MB49094D931267988E377A9A2E92EEA@VE1PR08MB4909.eurprd08.prod.outlook.com>
On Thu, 2023-09-07 at 10:48 +0000, Johannes Kirchmair wrote:
> Hey Florian,
>
> > -----Original Message-----
> > From: Florian Bezdeka <florian.bezdeka@siemens.com>
> [...]
> > > +COBALT_SYSCALL32emu(sigaction, current,
> > > + (int sig, void __user *handler, void __user *restorer))
> > > +{
> > > + struct cobalt_ppd *sys_ppd = cobalt_ppd_get(0);
> > > +
> > > + if (sig < 0 || sig >= _NSIG)
> > > + return -EINVAL;
> > > +
> > > + sys_ppd->sighand[sig] = handler;
> > > +
> > > + if (!sys_ppd->sigrestorer)
> > > + sys_ppd->sigrestorer = restorer;
> > > +
> > > + return 0;
> > > +}
> > > +
> >
> > You did not touch the syscall32-table.h (x86 specific), so I would
> > expect that your compat support is broken right now. You should end up
> > in the "native" so x86_64 implementation. That brings me to the next
> > question:
> Checked this and you are right, we end up in the "native" implementation of the syscall.
> Will drop the compat syscall.
Fine.
>
> >
> > Can't we avoid a special compat case here? The pointers themselfs are
> > corrected by the syscall entry machinery but the memory pointed to is
> > not. So is the memory pointed to by handler and restorer different in
> > terms of memory layout/padding?
> We don’t access the memory pointed to from kernel space, so this should not be imported or am I missing something?
This is obsolete. We could drop the compat case.
>
> >
> > In addition you should update kernel/cobalt/trace/cobalt-posix.h to get
> > proper trace support.
> Changed the following define to look like this:
> #define __cobalt_syscall_name(__nr) \
> __print_symbolic((__nr), \
> ....
> __cobalt_symbolic_syscall(pselect64), \
> __cobalt_symbolic_syscall(sigreturn), \
> __cobalt_symbolic_syscall(sigaction))
>
> Is this sufficient or do I have to change something else?
Yes, that should be sufficient.
>
> Best regards Johannes
>
>
next prev parent reply other threads:[~2023-09-11 8:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 10:18 [PATCH 1/3] [POC] test implementaion of rt-signals Johannes Kirchmair
2023-08-16 10:18 ` [PATCH 2/3] [POC] Add rt_signal test Johannes Kirchmair
2023-08-16 10:18 ` [PATCH 3/3] [POC] add a tool to measure rt_signal latency Johannes Kirchmair
2023-08-16 11:24 ` [PATCH 1/3] [POC] test implementaion of rt-signals Florian Bezdeka
2023-08-16 11:36 ` Jan Kiszka
2023-08-16 11:59 ` Johannes Kirchmair
2023-09-07 10:48 ` Johannes Kirchmair
2023-09-11 8:41 ` Florian Bezdeka [this message]
2023-09-01 12:00 ` Jan Kiszka
2023-09-01 13:38 ` Jan Kiszka
2023-09-04 6:55 ` Johannes Kirchmair
2023-09-07 13:39 ` Jan Kiszka
2023-09-07 13:58 ` Johannes Kirchmair
2023-09-01 13:51 ` Jan Kiszka
2023-09-01 14:11 ` Jan Kiszka
2023-09-04 7:04 ` Johannes Kirchmair
2024-03-05 15:54 ` Richard Weinberger
2024-03-05 17:05 ` Jan Kiszka
2024-03-05 17:14 ` Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 10:50 Johannes Kirchmair
2023-09-08 10:54 ` Johannes Kirchmair
2023-09-09 11:35 ` Jan Kiszka
2023-05-09 13:13 Johannes Kirchmair
2023-05-09 13:17 ` Johannes Kirchmair
2023-05-12 17:38 ` Jan Kiszka
2023-05-15 6:50 ` Johannes Kirchmair
2023-05-15 10:38 ` Jan Kiszka
2023-05-16 6:46 ` Johannes Kirchmair
2023-05-16 6:52 ` Jan Kiszka
2023-08-09 9:50 ` Schaffner, Tobias
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=7212c5ca53968beeee4753065fbbb700e1ccdbd6.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=johannes.kirchmair@sigmatek.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 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 NNTP newsgroup(s).