From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0yRT-0007Jr-LZ for qemu-devel@nongnu.org; Fri, 24 Feb 2012 11:56:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S0yRO-00029z-0c for qemu-devel@nongnu.org; Fri, 24 Feb 2012 11:56:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:26460) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0yRN-00029v-Ot for qemu-devel@nongnu.org; Fri, 24 Feb 2012 11:56:17 -0500 Date: Fri, 24 Feb 2012 14:56:16 -0200 From: Luiz Capitulino Message-ID: <20120224145616.7380db64@doriath.home> In-Reply-To: <4F47BE5B.6010602@codemonkey.ws> References: <1329506504-29152-1-git-send-email-lcapitulino@redhat.com> <1329506504-29152-6-git-send-email-lcapitulino@redhat.com> <4F44EC3B.9090902@redhat.com> <20120223101717.5e5886b9@doriath.home> <4F47B43C.8050008@codemonkey.ws> <20120224143911.018b2073@doriath.home> <4F47BE5B.6010602@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 5/5] qmp: add DEVICE_TRAY_MOVED event List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , pbonzini@redhat.com, eblake@redhat.com, Markus Armbruster , qemu-devel@nongnu.org On Fri, 24 Feb 2012 10:44:11 -0600 Anthony Liguori wrote: > > I'm asking because the conversion of events to the qapi is not too far away, > > but I think that using QOM will somewhat deprecate the code you have in the > > glib branch (besides having to wait for 1.2)? > > I have some vague ideas about what to do here. One thought would be to have a > standard notifier mechanism in Object that was advertised as a property type. > We could then provide an interface via QMP to [un]subscribe to a notifier property. This seems to be a good match with your previous ideas, implemented in the glib branch. But then subsystems/devices emitting events will have to be converted to QOM first... > I won't get to this until the 1.2 time frame though. My goals for 1.1 are to > get qbus conversions merged and refactor IRQs/MemoryRegions to use QOM. If time > permits, also refactor the PC to better use QOM. > > If someone wants to tackle events in QOM, I'd be happy to provide some > suggestions on where to start. I'd like to hear about it, but I'm not sure when I'll start working on it.