[Xen-changelog] [xen-unstable] Actually set a HVM domain's time offset when it sets the RTC

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1237382682 0
# Node ID b8242b82b561712cbd509ad015702d74fcc07e56
# Parent  c1aa7b9d48422526d14911a4dea86bff15e14592
Actually set a HVM domain's time offset when it sets the RTC

Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
---
 xen/arch/x86/hvm/rtc.c |    7 +++++++
 1 files changed, 7 insertions(+)

diff -r c1aa7b9d4842 -r b8242b82b561 xen/arch/x86/hvm/rtc.c
--- a/xen/arch/x86/hvm/rtc.c    Wed Mar 18 11:51:30 2009 +0000
+++ b/xen/arch/x86/hvm/rtc.c    Wed Mar 18 13:24:42 2009 +0000
@@ -160,6 +160,7 @@ static void rtc_set_time(RTCState *s)
 static void rtc_set_time(RTCState *s)
 {
     struct tm *tm = &s->current_tm;
+    struct domain *d = vrtc_domain(s);
     unsigned long before, after; /* XXX s_time_t */
       
     ASSERT(spin_is_locked(&s->lock));
@@ -180,6 +181,12 @@ static void rtc_set_time(RTCState *s)
 
     after = mktime(tm->tm_year, tm->tm_mon, tm->tm_mday,
                    tm->tm_hour, tm->tm_min, tm->tm_sec);
+
+    /* We use the guest's setting of the RTC to define the local-time 
+     * offset for this domain. */
+    d->time_offset_seconds += (after - before);
+    update_domain_wallclock_time(d);
+    /* Also tell qemu-dm about it so it will be remembered for next boot. */
     send_timeoffset_req(after - before);
 }
 

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog