On Thu, May 2, 2019 at 7:30 AM Jan Beulich wrote:
>
> >>> On 02.05.19 at 15:09, wrote:
> > That said I don't have a use for idt and gdtr_limit that warrants
> > having to receive it via the vm_event structure
>
> So what use if the GDT base without the limit? Are you silently
> assuming all prese
>>> On 02.05.19 at 15:09, wrote:
> That said I don't have a use for idt and gdtr_limit that warrants
> having to receive it via the vm_event structure
So what use if the GDT base without the limit? Are you silently
assuming all presently loaded selectors are (still) within limits?
Jan
___
>>> On 02.05.19 at 15:23, wrote:
> My point is, at the moment it's fine to skip idtr if it's not required
> by Jan, but if we do add either then let's please add both _base and _limit.
No, it's not a requirement I mean to put up (and I'm not in the
position to either, as I'm not the maintainer o
On 5/2/19 4:09 PM, Tamas K Lengyel wrote:
On Thu, May 2, 2019 at 2:57 AM Jan Beulich wrote:
On 02.05.19 at 10:25, wrote:
On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
Receiving this register is useful for introspecting 32-bit Windows when the
event being trapped happened while in ring3.
Signe
On Thu, May 2, 2019 at 2:57 AM Jan Beulich wrote:
>
> >>> On 02.05.19 at 10:25, wrote:
> > On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
> >> Receiving this register is useful for introspecting 32-bit Windows when the
> >> event being trapped happened while in ring3.
> >>
> >> Signed-off-by: Tamas K
On 5/2/19 11:52 AM, Andrew Cooper wrote:
On 02/05/2019 09:25, Razvan Cojocaru wrote:
On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
Receiving this register is useful for introspecting 32-bit Windows
when the
event being trapped happened while in ring3.
Signed-off-by: Tamas K Lengyel
Cc: Razvan C
>>> On 02.05.19 at 10:25, wrote:
> On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
>> Receiving this register is useful for introspecting 32-bit Windows when the
>> event being trapped happened while in ring3.
>>
>> Signed-off-by: Tamas K Lengyel
>> Cc: Razvan Cojocaru
>> Cc: Tamas K Lengyel
>> Cc:
On 02/05/2019 09:25, Razvan Cojocaru wrote:
> On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
>> Receiving this register is useful for introspecting 32-bit Windows
>> when the
>> event being trapped happened while in ring3.
>>
>> Signed-off-by: Tamas K Lengyel
>> Cc: Razvan Cojocaru
>> Cc: Tamas K Leng
On 5/2/19 2:57 AM, Tamas K Lengyel wrote:
Receiving this register is useful for introspecting 32-bit Windows when the
event being trapped happened while in ring3.
Signed-off-by: Tamas K Lengyel
Cc: Razvan Cojocaru
Cc: Tamas K Lengyel
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
Cc: Roger
Receiving this register is useful for introspecting 32-bit Windows when the
event being trapped happened while in ring3.
Signed-off-by: Tamas K Lengyel
Cc: Razvan Cojocaru
Cc: Tamas K Lengyel
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
Cc: Roger Pau Monne
---
xen/arch/x86/vm_event.c
10 matches
Mail list logo