From: Frank Rowand <frank.rowand@gmail.com>
To: frank.rowand@am.sony.com
Cc: Peter LaDow <petela@gocougs.wsu.edu>,
Frank Rowand <frank.rowand@gmail.com>,
linux-rt-users@vger.kernel.org
Subject: Re: Interrupt Bottom Half Scheduling
Date: Tue, 15 Feb 2011 10:40:17 -0800 [thread overview]
Message-ID: <4D5AC891.9000705@am.sony.com> (raw)
In-Reply-To: <4D5AC80F.1090205@am.sony.com>
On 02/15/11 10:38, Frank Rowand wrote:
> try_to_wake_up() is in the scheduler code (kernel/sched.c), but it is
> not "the scheduler". If the task is not already running,
> try_to_wake_up() will put the task on the run queue and set it's state
> to TASK_RUNNING. If the priority of the newly woken thread was higher
> than the current thread, then the newly woken thread would preempt
> current. If a preemption occurred, then TIF_NEED_RESCHED is set.
Oops, I slipped into using "thread" instead of "task". Just substitue
"task" for each occurance of "thread" in that paragraph.
> The actual "schedule" will occur on the exit path of the interrupt
> only if TIF_NEED_RESCHED is set (see the call of preempt_schedule_irq()).
next prev parent reply other threads:[~2011-02-15 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 22:31 Interrupt Bottom Half Scheduling Peter LaDow
2011-02-14 23:04 ` Sven-Thorsten Dietrich
2011-02-14 23:08 ` Peter LaDow
2011-02-14 23:35 ` Sven-Thorsten Dietrich
2011-02-14 23:42 ` Peter LaDow
2011-02-15 0:50 ` Sven-Thorsten Dietrich
2011-02-14 23:30 ` Frank Rowand
2011-02-15 1:10 ` Peter LaDow
2011-02-15 1:58 ` Frank Rowand
2011-02-15 2:16 ` Frank Rowand
2011-02-15 16:42 ` Peter LaDow
2011-02-15 18:38 ` Frank Rowand
2011-02-15 18:40 ` Frank Rowand [this message]
2011-02-15 19:12 ` Peter LaDow
2011-02-15 19:35 ` Frank Rowand
2011-02-16 20:18 ` Peter LaDow
2011-02-15 8:40 ` Armin Steinhoff
2011-02-15 8:23 ` Uwe Kleine-König
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=4D5AC891.9000705@am.sony.com \
--to=frank.rowand@gmail.com \
--cc=frank.rowand@am.sony.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=petela@gocougs.wsu.edu \
/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.