Messages in this thread | | | Subject | Re: The O(1) scheduler breaks UML | Date | Sun, 13 Jan 2002 23:49:16 -0500 | From | Jeff Dike <> |
| |
davidel@xmailserver.org said: > Yes, this should work : > if (likely(prev != next)) { > rq->nr_switches++; > rq->curr = next; > next->cpu = prev->cpu; > spin_unlock_irq(&rq->lock); > context_switch(prev, next); > } else > spin_unlock_irq(&rq->lock); > and there's no need for barrier() and rq reload in this way.
Yup, UML works much better with that.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |