On 26/03/2018 14:25, Wanpeng Li wrote:
> 2018-03-23 23:04 GMT+08:00 Paolo Bonzini :
>> On 23/03/2018 15:27, Wanpeng Li wrote:
>>> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
On 22/03/18 13:39, Wanpeng Li wrote:
> 2018-03-22 20:38 GMT+08:00
On 26/03/2018 14:25, Wanpeng Li wrote:
> 2018-03-23 23:04 GMT+08:00 Paolo Bonzini :
>> On 23/03/2018 15:27, Wanpeng Li wrote:
>>> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
On 22/03/18 13:39, Wanpeng Li wrote:
> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
>> On 22/03/2018 12:04, Andrew
2018-03-23 23:04 GMT+08:00 Paolo Bonzini :
> On 23/03/2018 15:27, Wanpeng Li wrote:
>> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>>> On 22/03/18 13:39, Wanpeng Li wrote:
2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
> On
2018-03-23 23:04 GMT+08:00 Paolo Bonzini :
> On 23/03/2018 15:27, Wanpeng Li wrote:
>> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>>> On 22/03/18 13:39, Wanpeng Li wrote:
2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
> On 22/03/2018 12:04, Andrew Cooper wrote:
>> We've got a Force
On 23/03/2018 15:27, Wanpeng Li wrote:
> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>> On 22/03/18 13:39, Wanpeng Li wrote:
>>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force
On 23/03/2018 15:27, Wanpeng Li wrote:
> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>> On 22/03/18 13:39, Wanpeng Li wrote:
>>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>
On 23/03/18 14:27, Wanpeng Li wrote:
> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>> On 22/03/18 13:39, Wanpeng Li wrote:
>>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force Emulation
On 23/03/18 14:27, Wanpeng Li wrote:
> 2018-03-22 21:53 GMT+08:00 Andrew Cooper :
>> On 22/03/18 13:39, Wanpeng Li wrote:
>>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>
2018-03-22 21:53 GMT+08:00 Andrew Cooper :
> On 22/03/18 13:39, Wanpeng Li wrote:
>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
>>> On 22/03/2018 12:04, Andrew Cooper wrote:
We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
2018-03-22 21:53 GMT+08:00 Andrew Cooper :
> On 22/03/18 13:39, Wanpeng Li wrote:
>> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
>>> On 22/03/2018 12:04, Andrew Cooper wrote:
We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
magic. Originally, this was used for PV guests
On 22/03/18 13:39, Wanpeng Li wrote:
> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
>> On 22/03/2018 12:04, Andrew Cooper wrote:
>>> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>>> magic. Originally, this was used for PV guests to explicitly request an
>>>
On 22/03/18 13:39, Wanpeng Li wrote:
> 2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
>> On 22/03/2018 12:04, Andrew Cooper wrote:
>>> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>>> magic. Originally, this was used for PV guests to explicitly request an
>>> emulated CPUID, but
2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
> On 22/03/2018 12:04, Andrew Cooper wrote:
>> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>> magic. Originally, this was used for PV guests to explicitly request an
>> emulated CPUID, but I extended it to HVM
2018-03-22 20:38 GMT+08:00 Paolo Bonzini :
> On 22/03/2018 12:04, Andrew Cooper wrote:
>> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
>> magic. Originally, this was used for PV guests to explicitly request an
>> emulated CPUID, but I extended it to HVM guests for "emulate
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
> magic. Originally, this was used for PV guests to explicitly request an
> emulated CPUID, but I extended it to HVM guests for "emulate the next
> instruction", after we had some guest
On 22/03/2018 12:04, Andrew Cooper wrote:
> We've got a Force Emulation Prefix (ud2a; .ascii "xen") for doing
> magic. Originally, this was used for PV guests to explicitly request an
> emulated CPUID, but I extended it to HVM guests for "emulate the next
> instruction", after we had some guest
2018-03-22 19:04 GMT+08:00 Andrew Cooper :
> On 22/03/2018 10:42, Paolo Bonzini wrote:
>> On 22/03/2018 11:19, Andrew Cooper wrote:
>>> On 22/03/2018 10:07, Paolo Bonzini wrote:
On 22/03/2018 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
2018-03-22 19:04 GMT+08:00 Andrew Cooper :
> On 22/03/2018 10:42, Paolo Bonzini wrote:
>> On 22/03/2018 11:19, Andrew Cooper wrote:
>>> On 22/03/2018 10:07, Paolo Bonzini wrote:
On 22/03/2018 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Explicit segment overides other than %fs
On 22/03/2018 10:42, Paolo Bonzini wrote:
> On 22/03/2018 11:19, Andrew Cooper wrote:
>> On 22/03/2018 10:07, Paolo Bonzini wrote:
>>> On 22/03/2018 09:34, Wanpeng Li wrote:
From: Wanpeng Li
Explicit segment overides other than %fs and %gs are documented as
On 22/03/2018 10:42, Paolo Bonzini wrote:
> On 22/03/2018 11:19, Andrew Cooper wrote:
>> On 22/03/2018 10:07, Paolo Bonzini wrote:
>>> On 22/03/2018 09:34, Wanpeng Li wrote:
From: Wanpeng Li
Explicit segment overides other than %fs and %gs are documented as ignored
by
On 22/03/2018 11:19, Andrew Cooper wrote:
> On 22/03/2018 10:07, Paolo Bonzini wrote:
>> On 22/03/2018 09:34, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>>
>>> Explicit segment overides other than %fs and %gs are documented as ignored
>>> by
>>> both Intel and AMD.
>>>
>>> In
On 22/03/2018 11:19, Andrew Cooper wrote:
> On 22/03/2018 10:07, Paolo Bonzini wrote:
>> On 22/03/2018 09:34, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>>
>>> Explicit segment overides other than %fs and %gs are documented as ignored
>>> by
>>> both Intel and AMD.
>>>
>>> In practice, this means
On 22/03/2018 10:07, Paolo Bonzini wrote:
> On 22/03/2018 09:34, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> Explicit segment overides other than %fs and %gs are documented as ignored by
>> both Intel and AMD.
>>
>> In practice, this means that:
>>
>> * Explicit uses of
On 22/03/2018 10:07, Paolo Bonzini wrote:
> On 22/03/2018 09:34, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> Explicit segment overides other than %fs and %gs are documented as ignored by
>> both Intel and AMD.
>>
>> In practice, this means that:
>>
>> * Explicit uses of %ss don't actually yield
On 22/03/2018 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Explicit segment overides other than %fs and %gs are documented as ignored by
> both Intel and AMD.
>
> In practice, this means that:
>
> * Explicit uses of %ss don't actually yield #SS[0] for non-canonical
>
On 22/03/2018 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Explicit segment overides other than %fs and %gs are documented as ignored by
> both Intel and AMD.
>
> In practice, this means that:
>
> * Explicit uses of %ss don't actually yield #SS[0] for non-canonical
>memory references.
From: Wanpeng Li
Explicit segment overides other than %fs and %gs are documented as ignored by
both Intel and AMD.
In practice, this means that:
* Explicit uses of %ss don't actually yield #SS[0] for non-canonical
memory references.
* Explicit uses of %{e,c,d}s
From: Wanpeng Li
Explicit segment overides other than %fs and %gs are documented as ignored by
both Intel and AMD.
In practice, this means that:
* Explicit uses of %ss don't actually yield #SS[0] for non-canonical
memory references.
* Explicit uses of %{e,c,d}s don't override
28 matches
Mail list logo