>>> On 04.01.17 at 16:05, wrote:
> On 04/01/17 14:22, Jan Beulich wrote:
> On 04.01.17 at 13:39, wrote:
>>> struct cpuid_policy will eventually be a complete replacement for the
>>> cpuids[]
>>> array, with a fixed layout and named fields to allow O(1) access to specific
>>> information.
>>>
On 04/01/17 14:22, Jan Beulich wrote:
On 04.01.17 at 13:39, wrote:
>> struct cpuid_policy will eventually be a complete replacement for the
>> cpuids[]
>> array, with a fixed layout and named fields to allow O(1) access to specific
>> information.
>>
>> For now, the CPUID content is capped a
>>> On 04.01.17 at 13:39, wrote:
> struct cpuid_policy will eventually be a complete replacement for the cpuids[]
> array, with a fixed layout and named fields to allow O(1) access to specific
> information.
>
> For now, the CPUID content is capped at the 0xd and 0x801c leaves, which
> matche
struct cpuid_policy will eventually be a complete replacement for the cpuids[]
array, with a fixed layout and named fields to allow O(1) access to specific
information.
For now, the CPUID content is capped at the 0xd and 0x801c leaves, which
matches the maximum policy that the toolstack will g
