Thank you, Eric.
I want to improve this feature as follow , in order to simplify the code.
1. set up a hashtable of event names to a appropriate struct.
when user register an event, this event name will be added to
this hashtable.
and maybe different connection will add the same
On 12/16/2011 09:58 AM, shao...@linux.vnet.ibm.com wrote:
From: ShaoHe Feng shao...@linux.vnet.ibm.com
Basically, this feature can go along with qemu monitor passthrough.
That way, if we use new commands in the monitor that generate new events, we
want some way to receive those new events
On 12/16/2011 09:58 AM, shao...@linux.vnet.ibm.com wrote:
From: ShaoHe Feng shao...@linux.vnet.ibm.com
Basically, this feature can go along with qemu monitor passthrough.
That way, if we use new commands in the monitor that generate new events, we
want some way to receive those new events
On Wed, Jan 25, 2012 at 02:16:14PM -0700, Eric Blake wrote:
On 12/16/2011 09:58 AM, shao...@linux.vnet.ibm.com wrote:
From: ShaoHe Feng shao...@linux.vnet.ibm.com
Basically, this feature can go along with qemu monitor passthrough.
That way, if we use new commands in the monitor that
Please remember to Cc: the libvirt list as well so that others may contribute to
the discussion.
On Sat, Dec 17, 2011 at 12:58:58AM +0800, ShaoHe Feng wrote:
From: ShaoHe Feng shao...@linux.vnet.ibm.com
Basically, this feature can go along with qemu monitor passthrough.
That way, if we use
From: ShaoHe Feng shao...@linux.vnet.ibm.com
Basically, this feature can go along with qemu monitor passthrough.
That way, if we use new commands in the monitor that generate new events, we
want some way to receive those new events too.
Signed-off-by: ShaoHe Feng shao...@linux.vnet.ibm.com
---
there are still some questions:
In my code the add new libvirt_qemu specific events and the former
libvirt events share the same event queue.
so in libvirtd, the qemuDomainEventFlush will dispatch these two kinds
of event.
so should I add new event queue for the new libvirt_qemu specific
events,
