From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ2xy-0003GU-Jj for qemu-devel@nongnu.org; Tue, 23 Jun 2009 06:11:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ2xu-0003E6-BZ for qemu-devel@nongnu.org; Tue, 23 Jun 2009 06:11:02 -0400 Received: from [199.232.76.173] (port=51410 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ2xt-0003Dm-Uc for qemu-devel@nongnu.org; Tue, 23 Jun 2009 06:10:57 -0400 Received: from mx20.gnu.org ([199.232.41.8]:61856) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MJ2xt-0003oO-If for qemu-devel@nongnu.org; Tue, 23 Jun 2009 06:10:57 -0400 Received: from mx2.redhat.com ([66.187.237.31]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ2xs-0002av-T5 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 06:10:57 -0400 Message-ID: <4A40AA65.2090501@redhat.com> Date: Tue, 23 Jun 2009 13:11:49 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20090623012911.16b8c4d5@doriath> <20090623100839.GF6881@redhat.com> In-Reply-To: <20090623100839.GF6881@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 06/11] QMP: Introduce asynchronous events infrastructure List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: aliguori@us.ibm.com, ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino On 06/23/2009 01:08 PM, Daniel P. Berrange wrote: > On Tue, Jun 23, 2009 at 01:29:11AM -0300, Luiz Capitulino wrote: > >> It is just an exported function that will be used by other subsystems >> to print specific events to the output buffer. >> >> This is based in ideas by Amit Shah. >> >> Signed-off-by: Luiz Capitulino >> > > As per my mail to the lead message in this thread, I'm thinking it > might be valuable to include a timestamp with all events, and command > replies. A 64-bit seconds-since-epoch prefix on all replies, no need > for a human-format timestamp > A bit of an overkill... seconds.nanoseconds. -- error compiling committee.c: too many arguments to function