From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20200407154117.5D7D71C2@centrum.cz> <20200407171816.E0B3979D@centrum.cz> <20200408114406.6119E0D9@centrum.cz> In-Reply-To: <20200408114406.6119E0D9@centrum.cz> From: Richard Weinberger Date: Wed, 8 Apr 2020 12:06:06 +0200 Message-ID: Subject: Re: rt_task_unblock() POSIX alternative Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Petr_=C4=8Cervenka?= Cc: Jan Kiszka , Xenomai On Wed, Apr 8, 2020 at 11:44 AM Petr =C4=8Cervenka wrote= : > > > Use pthread_kill() plus a custom signal. Such as SIGRTMIN + 2. > Calling of kill() or pthread_kill() does not help. Nothing is able to int= errupt read() from timerfd (only pthread_cancel). Do I have to prepare the = task or timerfd to be interruptible by a signal? Using the signal you can interrupt the system call. Of course only if the system call is currently interruptable. pthread_cancel() in async mode also just sends a signal (SIGCANCEL) and terminates the thread in a more or less sane way. --=20 Thanks, //richard