Jeremy Fitzhardinge wrote: > Well, I was thinking option #4: the hypervisor setup code calls > set_fixmap_top() as part of its setup (ie, when it fills out the > paravirtops structure). That way the hypervisor-specific code can use > whatever mechanism it wants to get that value, and if the hypervisor > doesn't care about the value (because it doesn't need to reserve > address space, as in 32-on-64) it needn't call anything, and the > default Linux value will stand. > > I guess it's almost exactly equivalent to #2, except we don't need to > define another paravirt interface. Sounds good to me. We need to have a discussion and spec out the exact steps to be taken during init / start-of-day. Zach
