No subject

Tue Mar 31 12:00:45 PDT 2009

`setPriorityThread' moves the thread to the back of the scheduling queue
(within its priority level), whereas `yieldThread' implicitly assumes
that the yielding thread is at the front of the queue.  Line 326

	threadQhead[TCTX(currentThread)->priority] = currentThread->next;

will set the queue head to null if the thread has called setPriority,
and all the threads at this priority level will be ignored in future
scheduling rounds.

(please forgive me if I've got the diagnosis wrong---I verified that
the queue head is indeed getting nulled out but I can't claim to
understand the mechansism in depth ...)

By the way, even if I stop the IFC code calling setPriority, it still
comes to a grinding halt when it gets to a wait()---probably a
different problem.

public class YieldTest extends Thread {
  private static boolean setPriorityPreYield;
  private static boolean setPriorityPostYield;

  private String diagName;
  private long last = 0;

  public YieldTest(String diagName) {
    this.diagName = diagName;

  public void run() {
    for (;;) {
      long now = System.currentTimeMillis();
      if (now - last > 1000) {
	last = now;

      if (setPriorityPreYield)


      if (setPriorityPostYield)

  public static void main(String[] args) {
    setPriorityPreYield = args[0].equals("y");
    setPriorityPostYield = args[1].equals("y");

    new YieldTest("a").start();
    new YieldTest("b").start();
    new YieldTest("c").start();

More information about the kaffe mailing list