Il 30/06/2014 17:03, Jan Kiszka ha scritto:
15.5.1:
"When examining segment attributes after a #VMEXIT:
[...]
• Retrieve the CPL from the CPL field in the VMCB, not from any segment
DPL."
It's only the fourth paragraph below the one I did read...
Paolo
--
To unsubscribe from this list: send t
On Mon, Jun 30, 2014 at 05:15:44PM +0200, Borislav Petkov wrote:
> On Mon, Jun 30, 2014 at 05:03:57PM +0200, Jan Kiszka wrote:
> > 15.5.1:
> >
> > "When examining segment attributes after a #VMEXIT:
> > [...]
> > • Retrieve the CPL from the CPL field in the VMCB, not from any segment
> > DPL."
>
On Mon, Jun 30, 2014 at 05:03:57PM +0200, Jan Kiszka wrote:
> 15.5.1:
>
> "When examining segment attributes after a #VMEXIT:
> [...]
> • Retrieve the CPL from the CPL field in the VMCB, not from any segment
> DPL."
Heey, it is even documented! :-P
--
Regards/Gruss,
Boris.
Sent from a fat
On 2014-06-30 17:01, Paolo Bonzini wrote:
> Il 29/06/2014 17:12, Jan Kiszka ha scritto:
>> From: Jan Kiszka
>>
>> We import the CPL via SS.DPL since ae9fedc793. However, we fail to
>> export it this way so far. This caused spurious guest crashes, e.g. of
>> Linux when accessing the vmport from gue
Il 29/06/2014 17:12, Jan Kiszka ha scritto:
From: Jan Kiszka
We import the CPL via SS.DPL since ae9fedc793. However, we fail to
export it this way so far. This caused spurious guest crashes, e.g. of
Linux when accessing the vmport from guest user space which triggered
register saving/restoring
On Sun, Jun 29, 2014 at 05:12:43PM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> We import the CPL via SS.DPL since ae9fedc793. However, we fail to
> export it this way so far. This caused spurious guest crashes, e.g. of
> Linux when accessing the vmport from guest user space which triggered
>
6 matches
Mail list logo