Re: [Xen-devel] [PATCH V4 05/13] xen: Rename mem_event to vm_event

2015-02-13 Thread Wei Liu
On Mon, Feb 09, 2015 at 07:53:30PM +0100, Tamas K Lengyel wrote: > In this patch we mechanically rename mem_event to vm_event. This patch > introduces no logic changes to the code. Using the name vm_event better > describes the intended use of this subsystem, which is not limited to memory > events

Re: [Xen-devel] [PATCH V4 05/13] xen: Rename mem_event to vm_event

2015-02-10 Thread Jan Beulich
>>> On 09.02.15 at 19:53, wrote: > In this patch we mechanically rename mem_event to vm_event. This patch > introduces no logic changes to the code. Using the name vm_event better > describes the intended use of this subsystem, which is not limited to memory > events. It can be used for off-loadin

Re: [Xen-devel] [PATCH V4 05/13] xen: Rename mem_event to vm_event

2015-02-09 Thread Daniel De Graaf
On 02/09/2015 01:53 PM, Tamas K Lengyel wrote: In this patch we mechanically rename mem_event to vm_event. This patch introduces no logic changes to the code. Using the name vm_event better describes the intended use of this subsystem, which is not limited to memory events. It can be used for off

[Xen-devel] [PATCH V4 05/13] xen: Rename mem_event to vm_event

2015-02-09 Thread Tamas K Lengyel
In this patch we mechanically rename mem_event to vm_event. This patch introduces no logic changes to the code. Using the name vm_event better describes the intended use of this subsystem, which is not limited to memory events. It can be used for off-loading the decision making logic into helper ap