Re: [Xen-devel] [PATCH V5 02/12] xen/mem_event: Cleanup mem_event ring names and domctls

2015-02-13 Thread Tamas K Lengyel
On Fri, Feb 13, 2015 at 6:53 PM, Andrew Cooper wrote: > On 13/02/15 16:33, Tamas K Lengyel wrote: > >> diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c >> index 339f8fe..5851c66 100644 >> --- a/xen/arch/x86/mm/p2m.c >> +++ b/xen/arch/x86/mm/p2m.c >> @@ -1501,7 +1501,7 @@ bool_t p2m_mem_a

Re: [Xen-devel] [PATCH V5 02/12] xen/mem_event: Cleanup mem_event ring names and domctls

2015-02-13 Thread Andrew Cooper
On 13/02/15 16:33, Tamas K Lengyel wrote: > diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c > index 339f8fe..5851c66 100644 > --- a/xen/arch/x86/mm/p2m.c > +++ b/xen/arch/x86/mm/p2m.c > @@ -1501,7 +1501,7 @@ bool_t p2m_mem_access_check(paddr_t gpa, unsigned long > gla, > gfn_unloc

[Xen-devel] [PATCH V5 02/12] xen/mem_event: Cleanup mem_event ring names and domctls

2015-02-13 Thread Tamas K Lengyel
The name of one of the mem_event rings still implies it is used only for memory accesses, which is no longer the case. It is also used to deliver various HVM events, thus the name "monitor" is more appropriate in this setting. The mem_event subop definitions are also shortened to be more meaningfu