From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cpuid
Date: Mon, 5 Apr 2010 12:54:54 -0700 [thread overview]
Message-ID: <z2tdd6fe68a1004051254r464628d3wbd3f212705d1847f@mail.gmail.com> (raw)
In-Reply-To: <9a544c3c9f1193cef83f624f82d51fae@brasstown.quanstro.net>
> good point. two reasons
> 1. if up != p, what do you sleep on? or do you mess
> with the innards of sched? seems dangerous
given that you can echo stop >ctl and then echo start >ctl
from outside the kernel, i don't see why you can't do
something similar from inside the kernel.
> in looking at this again, runproc doesn't test
> for p->wired when "cooperativly scheduling".
>
> /* cooperative scheduling until the clock ticks */
> if((p=m->readied) && p->mach==0 && p->state==Ready
> && runq[Nrq-1].head == nil && runq[Nrq-2].head == nil){
>
> ready() also appears not to check wired.
sure but those are bugs anyway and easy to fix.
russ
prev parent reply other threads:[~2010-04-05 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 2:43 erik quanstrom
2010-04-05 6:30 ` Russ Cox
2010-04-05 13:28 ` erik quanstrom
2010-04-05 19:54 ` Russ Cox [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=z2tdd6fe68a1004051254r464628d3wbd3f212705d1847f@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).