[lkml]   [2003]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] sched-cleanup-2.5.69-A0
Ingo Molnar wrote:
> so you really want to run every time there's idle time, but you also want
> to sleep until the event that causes some other thread to run, right?

Basically yes. When my idle thread has decided that the system
is really idle (i.e. if there are pending softirqs, it generates
an interrupt and yields), it contacts the simulator process
(outside the UML system), and puts the entire UML system to

The simulator can then mess with the UML system through ptrace.
When it's done, it may advance the time, and let the UML system
run again. If the time has changed, the UML system will
fast-forward jiffies, and possibly generate a timer interrupt.
Then it yields its timeslice, and the cycle begins anew.

There are no "outside" interrupts, so ultimately, the event
causing other threads to run also comes from my idle thread.

- Werner

/ Werner Almesberger, Buenos Aires, Argentina /
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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