On 05/11/15 12:26, Razvan Cojocaru wrote:
> On 11/05/2015 01:44 PM, Andrew Cooper wrote:
>> On 05/11/15 11:35, Andrei LUTAS wrote:
>>> The use-case is the following: whenever an EPT violation is triggered
>>> inside a monitored VM, the introspection logic needs to know how many
>>> bytes were acces
On 11/05/2015 04:05 PM, Andrew Cooper wrote:
> On 05/11/15 12:26, Razvan Cojocaru wrote:
>> On 11/05/2015 01:44 PM, Andrew Cooper wrote:
>>> On 05/11/15 11:35, Andrei LUTAS wrote:
The use-case is the following: whenever an EPT violation is triggered
inside a monitored VM, the introspectio
On 11/05/2015 01:44 PM, Andrew Cooper wrote:
> On 05/11/15 11:35, Andrei LUTAS wrote:
>> The use-case is the following: whenever an EPT violation is triggered
>> inside a monitored VM, the introspection logic needs to know how many
>> bytes were accessed (read/written). This is done by inspecting t
On 05/11/15 11:35, Andrei LUTAS wrote:
> On 11/5/2015 12:51 PM, Jan Beulich wrote:
> On 05.11.15 at 11:49, wrote:
>>> On 05/11/15 10:42, Jan Beulich wrote:
>>> On 05.11.15 at 10:52, wrote:
> I need to get the XSAVE size from userspace. The easiest way seems
> to be
> to use th
On 11/5/2015 12:51 PM, Jan Beulich wrote:
On 05.11.15 at 11:49, wrote:
On 05/11/15 10:42, Jan Beulich wrote:
On 05.11.15 at 10:52, wrote:
I need to get the XSAVE size from userspace. The easiest way seems to be
to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
not public
On 05/11/15 10:47, Razvan Cojocaru wrote:
> On 11/05/2015 12:42 PM, Jan Beulich wrote:
> On 05.11.15 at 10:52, wrote:
>>> I need to get the XSAVE size from userspace. The easiest way seems to be
>>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>>> not public / there's
>>> On 05.11.15 at 11:47, wrote:
> On 11/05/2015 12:42 PM, Jan Beulich wrote:
> On 05.11.15 at 10:52, wrote:
>>> I need to get the XSAVE size from userspace. The easiest way seems to be
>>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>>> not public / there's no xenc
>>> On 05.11.15 at 11:49, wrote:
> On 05/11/15 10:42, Jan Beulich wrote:
> On 05.11.15 at 10:52, wrote:
>>> I need to get the XSAVE size from userspace. The easiest way seems to be
>>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>>> not public / there's no xenctrl.h
On 05/11/15 10:42, Jan Beulich wrote:
On 05.11.15 at 10:52, wrote:
>> I need to get the XSAVE size from userspace. The easiest way seems to be
>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>> not public / there's no xenctrl.h wrapper for it.
> Before going into any
On 11/05/2015 12:42 PM, Jan Beulich wrote:
On 05.11.15 at 10:52, wrote:
>> I need to get the XSAVE size from userspace. The easiest way seems to be
>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>> not public / there's no xenctrl.h wrapper for it.
>
> Before going
>>> On 05.11.15 at 10:52, wrote:
> I need to get the XSAVE size from userspace. The easiest way seems to be
> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
> not public / there's no xenctrl.h wrapper for it.
Before going into any detail of the rest of your mail - any reas
Hello,
I need to get the XSAVE size from userspace. The easiest way seems to be
to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
not public / there's no xenctrl.h wrapper for it.
There's also struct hvm_hw_cpu_xsave, which I can get to, but it doesn't
have a size member:
54
12 matches
Mail list logo
