From: Steven Rostedt <rostedt@goodmis.org>
To: dmarkh@cfl.rr.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel-rt <linux-rt-users@vger.kernel.org>,
Mark Hounschell <markh@compro.net>
Subject: Re: timer signal loss on RT
Date: Sat, 10 Mar 2012 14:44:17 -0500 [thread overview]
Message-ID: <1331408658.23363.5.camel@frodo> (raw)
In-Reply-To: <4F5B40BB.9080305@cfl.rr.com>
On Sat, 2012-03-10 at 06:53 -0500, Mark Hounschell wrote:
> >
>
> Does ksoftirqd deliver timer signals in vanilla?
Sometimes :-)
Softirqs in vanilla run in interrupt context. Mostly on return from an
hardware interrupt handler, the softirqs are called and run anytime
interrupts are enabled (and bottom halves enabled). But if there's too
much work to do from the soft interrupt, then it pushes the rest of the
work to ksoftirqd. Which on vanilla runs as a normal SCHED_OTHER task.
In -rt, the hardware handlers are run as thread, and all softirqs are
handled by ksoftirqd. -rt does not process any softirqs in interrupt
context.
The answer to your question is, the timerd softirq runs mostly from
interrupt context, which will preempt your high priority CPU hog, but if
too much work is being done, it may defer it to ksoftirqd, where your
thread might block it. But chances are it wont.
-- Steve
prev parent reply other threads:[~2012-03-10 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 10:26 timer signal loss on RT Mark Hounschell
2012-03-10 11:08 ` Mike Galbraith
2012-03-10 11:34 ` Thomas Gleixner
2012-03-10 11:53 ` Mark Hounschell
2012-03-10 19:44 ` Steven Rostedt [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=1331408658.23363.5.camel@frodo \
--to=rostedt@goodmis.org \
--cc=dmarkh@cfl.rr.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=markh@compro.net \
--cc=tglx@linutronix.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