On 18/07/18 08:29, Jan Beulich wrote:
>>>> On 17.07.18 at 19:23, <[email protected]> wrote:
>> The vPMU logic isn't integrated into the CPUID policy logic (and still
>> requires a fair amount of work before it can be).
>>
>> The ARCH_PERFMON leaf was previously copied into all policies, unilaterally
>> overridden (to the same value in the general case) by the toolstack using
>> DOMCTL_set_cpuid, then unilaterally overridden again by Xen's runtime
>> logic (based on the boot time settings).
>>
>> The policy retrieved with DOMCTL_get_cpu_policy needs to be accurate, so take
>> the boot time settings into account when creating and clipping the toolstack
>> policy. The runtime logic is still required for now, to clip the maximum
>> reported version when necessary.
>>
>> Signed-off-by: Andrew Cooper <[email protected]>
> Reviewed-by: Jan Beulich <[email protected]>
>
> I guess you will want this backported?
It isn't actually a problem until {SYSCTL,DOMCTL}_{get,set}_cpu_policy
are in use.
~Andrew
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
