On 25/12/2016 07:47, Suravee Suthikulpanit wrote:
>
>
> On 12/12/16 01:37, Andrew Cooper wrote:
>> On 11/12/16 17:33, Boris Ostrovsky wrote:
>>> - andrew.coop...@citrix.com wrote:
>>>
On 09/12/16 19:55, Andrew Cooper wrote:
> On 09/12/16 19:55, Boris Ostrovsky wrote:
>> On
On 12/12/16 01:37, Andrew Cooper wrote:
On 11/12/16 17:33, Boris Ostrovsky wrote:
- andrew.coop...@citrix.com wrote:
On 09/12/16 19:55, Andrew Cooper wrote:
On 09/12/16 19:55, Boris Ostrovsky wrote:
On 12/09/2016 02:01 PM, Andrew Cooper wrote:
Hello,
While working on XSA-192, I
Hi Andrew/Boris,
On 12/12/16 01:37, Andrew Cooper wrote:
On 11/12/16 17:33, Boris Ostrovsky wrote:
- andrew.coop...@citrix.com wrote:
On 09/12/16 19:55, Andrew Cooper wrote:
On 09/12/16 19:55, Boris Ostrovsky wrote:
On 12/09/2016 02:01 PM, Andrew Cooper wrote:
Hello,
While working on
On 11/12/16 17:33, Boris Ostrovsky wrote:
> - andrew.coop...@citrix.com wrote:
>
>> On 09/12/16 19:55, Andrew Cooper wrote:
>>> On 09/12/16 19:55, Boris Ostrovsky wrote:
On 12/09/2016 02:01 PM, Andrew Cooper wrote:
> Hello,
>
> While working on XSA-192, I found a curious
- andrew.coop...@citrix.com wrote:
> On 09/12/16 19:55, Andrew Cooper wrote:
> > On 09/12/16 19:55, Boris Ostrovsky wrote:
> >> On 12/09/2016 02:01 PM, Andrew Cooper wrote:
> >>> Hello,
> >>>
> >>> While working on XSA-192, I found a curious thing. On AMD
> hardware, the
> >>> VMMCALL
On 09/12/16 19:55, Andrew Cooper wrote:
> On 09/12/16 19:55, Boris Ostrovsky wrote:
>> On 12/09/2016 02:01 PM, Andrew Cooper wrote:
>>> Hello,
>>>
>>> While working on XSA-192, I found a curious thing. On AMD hardware, the
>>> VMMCALL instruction appears to behave like a nop if executed in VM86
On 09/12/16 19:55, Boris Ostrovsky wrote:
> On 12/09/2016 02:01 PM, Andrew Cooper wrote:
>> Hello,
>>
>> While working on XSA-192, I found a curious thing. On AMD hardware, the
>> VMMCALL instruction appears to behave like a nop if executed in VM86
>> mode. All other processor modes work fine.
On 12/09/2016 02:01 PM, Andrew Cooper wrote:
> Hello,
>
> While working on XSA-192, I found a curious thing. On AMD hardware, the
> VMMCALL instruction appears to behave like a nop if executed in VM86
> mode. All other processor modes work fine.
>
> The documentation suggests it should be valid
Hello,
While working on XSA-192, I found a curious thing. On AMD hardware, the
VMMCALL instruction appears to behave like a nop if executed in VM86
mode. All other processor modes work fine.
The documentation suggests it should be valid in any situation, but I
never get a #VMEXIT from it.
