In scheduler::checkPendingNotifies(), the CVS version (I believe
the copy I'm looking at is the recent one), does anyone else find it odd
that the terminating condition is (pnip->myNext != NULL) yet pnip -- so
far as I can tell -- is never changed? Could someone who's got an intact
CVS tree point the debugger at this and figure out why the loop
terminates? (Is my copy of scheduler.cc right? Are the jbSLL items not
set up right, e.g. myNext is always NULL? Is the list of pending notifies
always empty (despite addPendingNotify() being called from threadable.cc?)
Have we, for some reason, only ever had a single thread in the pending
queue?) I'm asking because I just finished moving that code to the 'new'
scheduler, and realized, contrary to the comment, that it never did walk
the list, and I wanted to find out what was going on. Thanks.
-_Quinn
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
