Re: [Xen-devel] [PATCH] vm_event: Remove xc_mem_access_enable_emulate() and friends

2016-02-12 Thread Jan Beulich
>>> On 12.02.16 at 10:04, wrote: > --- a/xen/include/public/memory.h > +++ b/xen/include/public/memory.h > @@ -390,8 +390,6 @@ DEFINE_XEN_GUEST_HANDLE(xen_mem_paging_op_t); > #define XENMEM_access_op21 > #define XENMEM_access_op_set_access

Re: [Xen-devel] [PATCH] vm_event: Remove xc_mem_access_enable_emulate() and friends

2016-02-12 Thread Razvan Cojocaru
On 02/12/2016 11:10 AM, Jan Beulich wrote: On 12.02.16 at 10:04, wrote: >> --- a/xen/include/public/memory.h >> +++ b/xen/include/public/memory.h >> @@ -390,8 +390,6 @@ DEFINE_XEN_GUEST_HANDLE(xen_mem_paging_op_t); >> #define XENMEM_access_op21

[Xen-devel] [PATCH] vm_event: Remove xc_mem_access_enable_emulate() and friends

2016-02-12 Thread Razvan Cojocaru
xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate() are currently no-ops, that is all they do is set a flag that nobody else checks. The user can already set the EMULATE flags in the vm_event response if emulation is desired, and having an extra check above that is not inherently

Re: [Xen-devel] [PATCH] vm_event: Remove xc_mem_access_enable_emulate() and friends

2016-02-12 Thread Wei Liu
On Fri, Feb 12, 2016 at 11:04:34AM +0200, Razvan Cojocaru wrote: > xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate() > are currently no-ops, that is all they do is set a flag that > nobody else checks. The user can already set the EMULATE flags in > the vm_event response if