On 17/05/18 14:38, Jan Beulich wrote:
On 17.05.18 at 15:26, wrote:
>> On 17/05/18 14:20, Jan Beulich wrote:
>>> Just like for HVM the feature set should be used for EBX output, while
>>> EAX should be restricted to the low 16 bits and ECX/EDX should be zero.
>>>
>>> Short of there being white
>>> On 17.05.18 at 15:26, wrote:
> On 17/05/18 14:20, Jan Beulich wrote:
>> Just like for HVM the feature set should be used for EBX output, while
>> EAX should be restricted to the low 16 bits and ECX/EDX should be zero.
>>
>> Short of there being white listing in place just like on the HVM side,
On 17/05/18 14:20, Jan Beulich wrote:
> Just like for HVM the feature set should be used for EBX output, while
> EAX should be restricted to the low 16 bits and ECX/EDX should be zero.
>
> Short of there being white listing in place just like on the HVM side,
> also zap leaves 6, 9, and 0x8007
Just like for HVM the feature set should be used for EBX output, while
EAX should be restricted to the low 16 bits and ECX/EDX should be zero.
Short of there being white listing in place just like on the HVM side,
also zap leaves 6, 9, and 0x8007 as well as unknown / reserved ones.
Signed-off
