lkml.org 
[lkml]   [1999]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: lowlatency-2.2.13-A1 questions

On Thu, 2 Dec 1999, William Montgomery wrote:

> An interrupt can occur during the kernel schedule function
> just prior to the "__switch_to" function and the interrupt handler
> may add a new task to the run-queue and set current->need_resched.
> Then the current task gets switched out immediately and the need_resched
> flag is lost. Should the new task inherit need_resched in this
> case? Is this an oversight or is this intentional?

hm, this shouldnt happen, because it's not current->need_resched that gets
set, but cpu_curr(cpu)->need_resched. cpu_curr gets set atomically and
takes the value of the next process already before doing the switch_to().
So any new wakeup and potential ->need_resched setting should go to the
next process.

-- mingo


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.048 / U:1.308 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site