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, 7 Apr 2020 17:30:09 +0200 [thread overview]
Message-ID: <CAFLxGvx2EhOgUnB1VkW+7TendLUcsZ0XGGcwYhiPw7PcxwFkTw@mail.gmail.com> (raw)
In-Reply-To: <20200407171816.E0B3979D@centrum.cz>
On Tue, Apr 7, 2020 at 5:18 PM Petr Červenka via Xenomai
<xenomai@xenomai.org> wrote:
>
> Hello Jan.
> And if I don't want to totally remove the thread? Only to interrupt the waiting and react according to new events (like reconfiguring something or starting to wait on different resource).
> Is there some pthread_create... or sched_... parameter or flag, that the task's system call can be interruptible?
> And how to use the signals to interrupt it? Call of kill(task_pid, SIGINT) didn't helped.
Use pthread_kill() plus a custom signal. Such as SIGRTMIN + 2.
--
Thanks,
//richard
next prev parent reply other threads:[~2020-04-07 15: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 [this message]
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
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=CAFLxGvx2EhOgUnB1VkW+7TendLUcsZ0XGGcwYhiPw7PcxwFkTw@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.