Kernel code interrupted by Timer

[Peter Teoh]

On Sat, Feb 9, 2013 at 1:47 PM, anish kumar
.
>
> Timer interrupts is supposed to cause scheduling and scheduler may or
> may not pick up your last process(we always use the term "task" in
> kernel space) after handling timer interrupt.
> >
>

Sorry if I may disagree, correct me if wrong.   Timer interrupt and
scheduler is two different thing.   I just counted in the "drivers"
subdirectory, there are at least more than 200 places where "setup_timer()"
is called, and these have nothing to do with scheduling.   For eg,
heartbeat operation etc.  Not sure I misunderstood something?

-- 
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130209/e0e72c96/attachment.html