[Xen-devel] CPU and scheduler init, Part 2

[George Dunlap <dunlapg@xxxxxxxxx>]

Keir,

I made a cpu status notifier for sched_credit2() to actually read an
arrange the runqueue information, and found the next niggle: the
callbacks are not guaranteed to finish before the cpu tried to go
through the scheduler.  The callback notifiers are handled on the cpu
that issues the boot command (i.e., cpu 0 during boot), and there's no
interlock to prevent the booted cpu from continuing until the
notifiers have completed execution.

Making a simple interlock (similar to the one in __cpu_up()) allows
the system to boot properly.  Another possibility would be to run the
notifiers on the freshly booted cpu before calling into the scheduler,
rather than on the cpu that issued the cpu boot sequence.

Thoughts?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel