>>> On 13.08.15 at 13:00, <julien.gr...@citrix.com> wrote: > On 13/08/15 11:54, Jan Beulich wrote: >>>>> On 13.08.15 at 12:48, <zhaoshengl...@huawei.com> wrote: >>> On 2015/8/13 18:29, Christoffer Dall wrote: >>>> However, what about for other resources? Having code somewhere that >>>> says "hide this random piece of hardware if you're Xen dom0" sounds >>>> awful to me. I know it's only the serial port right now, but still. >>>> >>> It needs to modify MADT table according to dom0_max_vcpus and modify EFI >>> MMAP table according to dom0_mem. And modify FADT table to set >>> hypervisor_id as "XenVMM" to tell Dom0 that it runs on Xen hypervisor. >> >> None of this should be required: >> >> Unaltered MADT may (or should I say will) be needed to drive P- or >> C-states. > > We have to alter MADT for different reasons: > - restricting the number of vCPUs > - update the CPU bring up method > - changing the CPUID > > Maybe we should pass a backup but we don't support cpufreq driver right > now and it would need quite a look of work to do it (see [1]).
I.e. you intend to not even leave open the road there. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
