From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Bug or works as intended: signal behaviour on -RT
Date: Fri, 5 Oct 2018 13:07:25 +0200 [thread overview]
Message-ID: <20181005110725.jggf75junl7euf3c@linutronix.de> (raw)
In-Reply-To: <d5b58969-26d3-d32b-71f7-fdd437c06ee1@oth-regensburg.de>
On 2018-09-26 17:07:02 [+0200], Ralf Ramsauer wrote:
> Hi,
Hi,
> But if I synchronously send a SIGALRM via kill, it will immediately
> arrive. Even a sched_yield() in the busy loop won't help. In order to
> get the signal, I have to leave running/runable with usleep().
a sched_yield() will put you at the end of the runqueue. If this is the
only task in that queue then the task will go back on the CPU.
> Thanks
> Ralf
Sebastian
prev parent reply other threads:[~2018-10-05 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 15:07 Bug or works as intended: signal behaviour on -RT Ralf Ramsauer
2018-10-03 15:51 ` Thomas Gleixner
2018-10-05 11:07 ` Sebastian Andrzej Siewior [this message]
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=20181005110725.jggf75junl7euf3c@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=ralf.ramsauer@oth-regensburg.de \
/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).