Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-02-09 Thread Tamas K Lengyel
>>> --- a/xen/include/public/hvm/params.h >>> +++ b/xen/include/public/hvm/params.h >>> @@ -162,21 +162,6 @@ >>> */ >>> #define HVM_PARAM_ACPI_IOPORTS_LOCATION 19 >>> >>> -/* Enable blocking memory events, async or sync (pause vcpu until response) >>> - * onchangeonly indicates messages only on

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-02-05 Thread Tamas K Lengyel
>> +int monitor_domctl(struct xen_domctl_monitor_op *domctl, struct domain *d) >> +{ >> +/* >> + * At the moment only HVM domains are supported. However, event delivery >> + * could be extended to PV domains. See comments below. >> + */ >> +if ( !is_hvm_domain(d) ) >> +r

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-02-04 Thread Jan Beulich
>>> On 29.01.15 at 22:46, wrote: > --- /dev/null > +++ b/xen/arch/x86/monitor.c > @@ -0,0 +1,197 @@ > +/* > + * This program is free software; you can redistribute it and/or > + * modify it under the terms of the GNU General Public > + * License v2 as published by the Free Software Foundation. > +

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-02-03 Thread Tian, Kevin
> From: Tamas K Lengyel [mailto:tamas.leng...@zentific.com] > Sent: Friday, January 30, 2015 5:47 AM > > In preparation for allowing for introspecting ARM and PV domains the old > control interface via the hvm_op hypercall is retired. A new control > mechanism > is introduced via the domctl hyperc

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-02-02 Thread Ian Campbell
On Thu, 2015-01-29 at 22:46 +0100, Tamas K Lengyel wrote: > In preparation for allowing for introspecting ARM and PV domains the old > control interface via the hvm_op hypercall is retired. A new control mechanism > is introduced via the domctl hypercall: monitor_op. > > This patch aims to establi

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Tamas K Lengyel
On Fri, Jan 30, 2015 at 1:24 PM, Razvan Cojocaru wrote: > On 01/30/2015 01:45 PM, Tamas K Lengyel wrote: Ack, the plan was actually to replace all references to arch.hvm_domain.introspection_enabled with arch.monitor_options.mov_to_msr.extended_capture. I see I forgot to a

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Razvan Cojocaru
On 01/30/2015 01:45 PM, Tamas K Lengyel wrote: >>> >>> Ack, the plan was actually to replace all references to >>> arch.hvm_domain.introspection_enabled with >>> arch.monitor_options.mov_to_msr.extended_capture. I see I forgot to >>> actually fully follow through that plan but that's the intention

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Tamas K Lengyel
>> >> Ack, the plan was actually to replace all references to >> arch.hvm_domain.introspection_enabled with >> arch.monitor_options.mov_to_msr.extended_capture. I see I forgot to >> actually fully follow through that plan but that's the intention at >> least. So the functionality would remain, it w

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Razvan Cojocaru
On 01/30/2015 01:15 PM, Tamas K Lengyel wrote: > On Fri, Jan 30, 2015 at 12:07 PM, Razvan Cojocaru > wrote: >> On 01/30/2015 12:38 PM, Tamas K Lengyel wrote: >>> On Fri, Jan 30, 2015 at 8:58 AM, Razvan Cojocaru >>> wrote: On 01/29/2015 11:46 PM, Tamas K Lengyel wrote: > diff --git a/xen/

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Tamas K Lengyel
>> >> There are also places in patches yet to be published I've worked on >> where we gate things on introspection_enabled being != 0, so please >> don't remove it or have it misbehave. >> >> I'll look into the extended_capture option in case it will allow future >> removal of the MSR special case

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Tamas K Lengyel
On Fri, Jan 30, 2015 at 12:07 PM, Razvan Cojocaru wrote: > On 01/30/2015 12:38 PM, Tamas K Lengyel wrote: >> On Fri, Jan 30, 2015 at 8:58 AM, Razvan Cojocaru >> wrote: >>> On 01/29/2015 11:46 PM, Tamas K Lengyel wrote: diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c index c7a

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Razvan Cojocaru
On 01/30/2015 12:38 PM, Tamas K Lengyel wrote: > On Fri, Jan 30, 2015 at 8:58 AM, Razvan Cojocaru > wrote: >> On 01/29/2015 11:46 PM, Tamas K Lengyel wrote: >>> diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c >>> index c7a0bde..3b58700 100644 >>> --- a/xen/arch/x86/mm/p2m.c >>> +++ b/xe

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-30 Thread Tamas K Lengyel
On Fri, Jan 30, 2015 at 8:58 AM, Razvan Cojocaru wrote: > On 01/29/2015 11:46 PM, Tamas K Lengyel wrote: >> diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c >> index c7a0bde..3b58700 100644 >> --- a/xen/arch/x86/mm/p2m.c >> +++ b/xen/arch/x86/mm/p2m.c >> @@ -1445,15 +1445,6 @@ void p2m_v

Re: [Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-29 Thread Razvan Cojocaru
On 01/29/2015 11:46 PM, Tamas K Lengyel wrote: > diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c > index c7a0bde..3b58700 100644 > --- a/xen/arch/x86/mm/p2m.c > +++ b/xen/arch/x86/mm/p2m.c > @@ -1445,15 +1445,6 @@ void p2m_vm_event_emulate_check(struct vcpu *v, const > vm_event_response

[Xen-devel] [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl

2015-01-29 Thread Tamas K Lengyel
In preparation for allowing for introspecting ARM and PV domains the old control interface via the hvm_op hypercall is retired. A new control mechanism is introduced via the domctl hypercall: monitor_op. This patch aims to establish a base API on which future applications can build on. Suggested-