On Wed, Aug 16, 2017 at 6:43 AM, Razvan Cojocaru
wrote:
> On 16.08.2017 15:32, Tamas K Lengyel wrote:
>>
>> On Wed, Aug 16, 2017 at 12:07 AM, Razvan Cojocaru
>> wrote:
>>>
>>> On 08/16/2017 02:16 AM, Tamas K Lengyel wrote:
On Tue, Aug 15, 2017 at 2:06 AM, Jan Beulich wrote:
>>
On 08/16/2017 02:16 AM, Tamas K Lengyel wrote:
> On Tue, Aug 15, 2017 at 2:06 AM, Jan Beulich wrote:
> On 14.08.17 at 17:53, wrote:
>>> On Tue, Aug 8, 2017 at 2:27 AM, Alexandru Isaila
>>> wrote:
--- a/xen/arch/x86/hvm/hypercall.c
+++ b/xen/arch/x86/hvm/hypercall.c
@@ -155,6
On Tue, Aug 15, 2017 at 2:06 AM, Jan Beulich wrote:
On 14.08.17 at 17:53, wrote:
>> On Tue, Aug 8, 2017 at 2:27 AM, Alexandru Isaila
>> wrote:
>>> --- a/xen/arch/x86/hvm/hypercall.c
>>> +++ b/xen/arch/x86/hvm/hypercall.c
>>> @@ -155,6 +155,11 @@ int hvm_hypercall(struct cpu_user_regs *regs
>>> On 14.08.17 at 17:53, wrote:
> On Tue, Aug 8, 2017 at 2:27 AM, Alexandru Isaila
> wrote:
>> --- a/xen/arch/x86/hvm/hypercall.c
>> +++ b/xen/arch/x86/hvm/hypercall.c
>> @@ -155,6 +155,11 @@ int hvm_hypercall(struct cpu_user_regs *regs)
>> /* Fallthrough to permission check. */
>>
On Tue, Aug 8, 2017 at 2:27 AM, Alexandru Isaila
wrote:
>
> In some introspection usecases, an in-guest agent needs to communicate
> with the external introspection agent. An existing mechanism is
> HVMOP_guest_request_vm_event, but this is restricted to kernel usecases
> like all other hypercall
On Ma, 2017-08-08 at 12:27 +0100, Wei Liu wrote:
> On Tue, Aug 08, 2017 at 11:27:35AM +0300, Alexandru Isaila wrote:
> >
> > In some introspection usecases, an in-guest agent needs to
> > communicate
> > with the external introspection agent. An existing mechanism is
> > HVMOP_guest_request_vm_ev
On Tue, Aug 08, 2017 at 11:27:35AM +0300, Alexandru Isaila wrote:
> In some introspection usecases, an in-guest agent needs to communicate
> with the external introspection agent. An existing mechanism is
> HVMOP_guest_request_vm_event, but this is restricted to kernel usecases
> like all other hy
In some introspection usecases, an in-guest agent needs to communicate
with the external introspection agent. An existing mechanism is
HVMOP_guest_request_vm_event, but this is restricted to kernel usecases
like all other hypercalls.
Introduce a mechanism whereby the introspection agent can white