From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Petr Červenka" <grugh@centrum.cz>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@xenomai.org>
Subject: Re: rt_task_unblock() POSIX alternative
Date: Tue, 14 Apr 2020 10:30:17 +0200 [thread overview]
Message-ID: <CAFLxGvz7ewnVv57QiEfCG76tjGcJ5v9KSg0QNHwtMa0Hihp_dQ@mail.gmail.com> (raw)
In-Reply-To: <20200414101600.F9AA555D@centrum.cz>
On Tue, Apr 14, 2020 at 10:16 AM Petr Červenka <grugh@centrum.cz> wrote:
>
> Hello Richard.
> Sorry for late answer because of the Easter.
>
> > I gave your program a try.
> > With this changes it works (at least how I understand your test case).
> >
> > Task started
> > Set period: 5s
> > Task livind: 9.9e-05s
> > Waiting for join
> > Signal handler: 41
> > Signal handler end
> > Task livind: 0.999s
> > Task ended
> >
> > ...
>
> There has to be something with my version of Xenomai, IPIPE or configuration. Not even your example is working for me. Morover in your example output is clearly visible, that the first waiting is interrupted 9.9e-05s after first attempt to wait by some unknown signal. Such thing has never happened to me in POSIX, only in Alchemy.
I fear there seems to be a confusion between POSIX tasks and POSIX skin.
Is your goal programming Xenomai realtime threads using POSIX alike APIs?
Or are you looking for a pedant of rt_task_unblock() to unblock a
POSIX task, without Xenomai realtime threads?
The solution I provided is for the latter case.
--
Thanks,
//richard
next prev parent reply other threads:[~2020-04-14 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 13:41 rt_task_unblock() POSIX alternative Petr Červenka
2020-04-07 14:59 ` Jan Kiszka
2020-04-07 15:18 ` Petr Červenka
2020-04-07 15:29 ` Jan Kiszka
2020-04-07 15:30 ` Richard Weinberger
2020-04-08 9:44 ` Petr Červenka
2020-04-08 10:06 ` Richard Weinberger
2020-04-08 21:36 ` Richard Weinberger
2020-04-09 15:00 ` Petr Červenka
2020-04-09 16:13 ` Richard Weinberger
2020-04-09 18:10 ` Petr Červenka
2020-04-09 18:48 ` Richard Weinberger
2020-04-14 8:16 ` Petr Červenka
2020-04-14 8:30 ` Richard Weinberger [this message]
2020-04-14 9:10 ` Petr Červenka
2020-04-14 9:46 ` Richard Weinberger
2020-04-14 10:07 ` Jan Kiszka
2020-04-14 10:23 ` Richard Weinberger
2020-04-14 10:28 ` Jan Kiszka
2020-04-14 10:41 ` Richard Weinberger
2020-04-14 10:43 ` Jan Kiszka
2020-04-14 10:56 ` Richard Weinberger
2020-04-14 11:01 ` Jan Kiszka
2020-04-14 11:05 ` Richard Weinberger
2020-04-14 11:30 ` Jan Kiszka
2020-04-14 10:39 ` Petr Červenka
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=CAFLxGvz7ewnVv57QiEfCG76tjGcJ5v9KSg0QNHwtMa0Hihp_dQ@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=grugh@centrum.cz \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.org \
/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.