From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Np0q6-00056t-Iq for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:55:18 -0500 Received: from [199.232.76.173] (port=44488 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Np0q6-00055l-0c for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:55:18 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Np0q1-0001LY-Dl for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:55:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40385) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Np0q1-0001LS-1Y for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:55:13 -0500 Date: Tue, 9 Mar 2010 11:55:03 -0300 From: Luiz Capitulino Subject: Re: [Qemu-devel] [PATCH] QMP: Introduce RTC_CHANGE event Message-ID: <20100309115503.6a1e9335@redhat.com> In-Reply-To: <4B965919.1050404@codemonkey.ws> References: <20100225121144.10d30251@redhat.com> <4B965919.1050404@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org On Tue, 09 Mar 2010 08:20:09 -0600 Anthony Liguori wrote: > On 02/25/2010 09:11 AM, Luiz Capitulino wrote: > > Emitted whenever the RTC time changes. > > > > Signed-off-by: Luiz Capitulino > > > > Not that this change isn't acceptable, but I think we need to improve > how we handle these events in the future. > > > --- > > QMP/qmp-events.txt | 15 +++++++++++++++ > > hw/mc146818rtc.c | 2 ++ > > monitor.c | 3 +++ > > monitor.h | 1 + > > sysemu.h | 2 ++ > > vl.c | 9 +++++++++ > > 6 files changed, 32 insertions(+), 0 deletions(-) > > > > diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt > > index b0183f9..f64b42d 100644 > > --- a/QMP/qmp-events.txt > > +++ b/QMP/qmp-events.txt > > @@ -38,6 +38,21 @@ Example: > > { "event": "RESET", > > "timestamp": { "seconds": 1267041653, "microseconds": 9518 } } > > > > +RTC_CHANGE > > +---------- > > + > > +Emitted when the RTC time changes. > > + > > +Data: > > + > > +- "offset": delta against the host UTC in seconds (json-number) > > + > > +Example: > > + > > +{ "event": "RTC_CHANGE", > > + "data": { "offset": 78 }, > > + "timestamp": { "seconds": 1267020223, "microseconds": 435656 } } > > + > > SHUTDOWN > > -------- > > > > diff --git a/hw/mc146818rtc.c b/hw/mc146818rtc.c > > index 2616d0d..a537855 100644 > > --- a/hw/mc146818rtc.c > > +++ b/hw/mc146818rtc.c > > @@ -297,6 +297,8 @@ static void rtc_set_time(RTCState *s) > > tm->tm_mday = rtc_from_bcd(s, s->cmos_data[RTC_DAY_OF_MONTH]); > > tm->tm_mon = rtc_from_bcd(s, s->cmos_data[RTC_MONTH]) - 1; > > tm->tm_year = rtc_from_bcd(s, s->cmos_data[RTC_YEAR]) + s->base_year - 1900; > > + > > + rtc_change_mon_event(tm); > > } > > > > static void rtc_copy_date(RTCState *s) > > diff --git a/monitor.c b/monitor.c > > index b2f5842..20512da 100644 > > --- a/monitor.c > > +++ b/monitor.c > > @@ -423,6 +423,9 @@ void monitor_protocol_event(MonitorEvent event, QObject *data) > > case QEVENT_BLOCK_IO_ERROR: > > event_name = "BLOCK_IO_ERROR"; > > break; > > + case QEVENT_RTC_CHANGE: > > + event_name = "RTC_CHANGE"; > > + break; > > default: > > abort(); > > break; > > diff --git a/monitor.h b/monitor.h > > index 8cc21f5..aa51bd5 100644 > > --- a/monitor.h > > +++ b/monitor.h > > @@ -23,6 +23,7 @@ typedef enum MonitorEvent { > > QEVENT_VNC_INITIALIZED, > > QEVENT_VNC_DISCONNECTED, > > QEVENT_BLOCK_IO_ERROR, > > + QEVENT_RTC_CHANGE, > > QEVENT_MAX, > > } MonitorEvent; > > > > This is going against the direction that we're trying to take with > qdev. We're trying to modularize devices by having only the device > themselves know their existence. That's the beauty of things like -device. Okay, we need to integrate with qdev then, as you have already suggested. > The fact that we're putting knowledge of the RTC into monitor.[ch] and > vl.c is a step in the wrong direction. We really ought to be able to > generate device specific events entirely within the device. Perhaps qdev can export available events to the Monitor, but even then the Monitor will have to at least know what put on the wire (eg. the event's string name). This can't be on qdev, as it's protocol specific info. Also, just a small note, I've changed vl.c because RTC code is there (it should be on its own module).