On 05/08/2015 07:50 PM, Andrew Cooper wrote:
> On 06/05/15 18:12, Razvan Cojocaru wrote:
>> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
>> index 86f9885..8ad03c6 100644
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -6267,6 +6267,10 @@ long do_hvm_op(unsigned
On 06/05/15 18:12, Razvan Cojocaru wrote:
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index 86f9885..8ad03c6 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -6267,6 +6267,10 @@ long do_hvm_op(unsigned long op,
> XEN_GUEST_HANDLE_PARAM(void) arg)
>
On 05/08/2015 07:16 PM, Jan Beulich wrote:
On 06.05.15 at 19:12, wrote:
>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>
> Perhaps better VM_EVENT_REASON_GUEST_REQUEST?
It does sound better, I'll change it.
>> --- a/xen/arch/x86/hvm/event.c
>> +++ b/xen/arch/x86/hv
>>> On 06.05.15 at 19:12, wrote:
> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
Perhaps better VM_EVENT_REASON_GUEST_REQUEST?
> --- a/xen/arch/x86/hvm/event.c
> +++ b/xen/arch/x86/hvm/event.c
> @@ -167,6 +167,20 @@ void hvm_event_xsetbv(unsigned long xcr, uint64_t value)
> To answer your question, I haven't really looked closely at libxenvchan
> before, but our use case at least can't use it (we're injecting some
> code in the guest on the fly). Am I wrong in assuming libxenvchan also
> requires two PV domains talking to each other? The guests we're
> monitoring ar
On 05/07/2015 08:05 PM, Tamas K Lengyel wrote:
> Hi Razvan,
> I guess I don't really see into the setup you envision using this
> event-type with, but wouldn't it be possible to just use libxenvchan?
Hello Tamas,
This patch evolved from "xen: Support for VMCALL mem_events":
http://lists.xen.org/
Hi Razvan,
I guess I don't really see into the setup you envision using this
event-type with, but wouldn't it be possible to just use libxenvchan?
Tamas
On Wed, May 6, 2015 at 7:12 PM, Razvan Cojocaru
wrote:
> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
> sent via HVMOP_
Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
sent via HVMOP_request_vm_event. The guest can request that a
generic vm_event (containing only the vm_event-filled guest registers
as information) be sent to userspace by setting up the correct
registers and doing a VMCALL. For e
