From: Werner Almesberger <wa@almesberger.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] sched-cleanup-2.5.69-A0
Date: Mon, 19 May 2003 14:46:05 -0300 [thread overview]
Message-ID: <20030519144605.B1432@almesberger.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0305191900400.14615-100000@localhost.localdomain>; from mingo@elte.hu on Mon, May 19, 2003 at 07:02:38PM +0200
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
sleep.
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 wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
prev parent reply other threads:[~2003-05-19 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 8:25 [patch] sched-cleanup-2.5.69-A0 Ingo Molnar
2003-05-19 15:13 ` Werner Almesberger
2003-05-19 16:09 ` Ingo Molnar
2003-05-19 16:51 ` Werner Almesberger
2003-05-19 17:02 ` Ingo Molnar
2003-05-19 17:46 ` Werner Almesberger [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=20030519144605.B1432@almesberger.net \
--to=wa@almesberger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/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.