Re: [Xen-devel] CPU and scheduler init in Xen

[Keir Fraser <keir@xxxxxxx>]

On 07/12/2010 15:05, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:

> On the one hand that all makes sense, but on the other hand it seems
> really crazy not to have basic info like the CPU topology available to
> the scheduler when the data for that CPU is initialized, and have to
> either (1) have a third scheduler callback, "cpu actually initialized
> now", or (2) resort to hackish tricks to look stuff up later (as the
> credit1 scheduler does to set up timers).

Can't you hook off CPU_UP notifier, and update your topology stuff from
that? You can do that entirely within sched_credit2.c -- no need for extra
hooks added to sched_if. This would also localise the changes, which I think
is a good thing.

 -- Keir

> I was hoping to be able to rearrange stuff so that when alloc_pdata()
> is called, that cpu_to_socket() be ready, but it's not exactly clear
> the best way to do that.
> 
> Any advice on how to proceed, Keir?



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