From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20200407154117.5D7D71C2@centrum.cz> <20200407171816.E0B3979D@centrum.cz> In-Reply-To: <20200407171816.E0B3979D@centrum.cz> From: Richard Weinberger Date: Tue, 7 Apr 2020 17:30:09 +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 Tue, Apr 7, 2020 at 5:18 PM Petr =C4=8Cervenka via Xenomai wrote: > > Hello Jan. > And if I don't want to totally remove the thread? Only to interrupt the w= aiting and react according to new events (like reconfiguring something or s= tarting 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. --=20 Thanks, //richard