tree 302034680d5c7217c28d3b7dff025bd73eeee8c4
parent b65fe0356b5b732d7e1e0224c6a1cf2eb5255984
author Andre Detsch <adetsch@br.ibm.com> 1220562987 +0000
committer Jeremy Kerr <jk@ozlabs.org> 1220831083 +1000

powerpc/spufs: Fix possible scheduling of a context to multiple SPEs

We currently have a race when scheduling a context to a SPE -
after we have found a runnable context in spusched_tick, the same
context may have been scheduled by spu_activate().

This may result in a panic if we try to unschedule a context that has
been freed in the meantime.

This change exits spu_schedule() if the context has already been
scheduled, so we don't end up scheduling it twice.

Signed-off-by: Andre Detsch <adetsch@br.ibm.com>
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>