xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Rafal Wojtczuk <rafal@invisiblethingslab.com>
To: xen-devel@lists.xensource.com
Subject: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
Date: Thu, 1 Jul 2010 05:04:31 +0200	[thread overview]
Message-ID: <20100701030431.GB1431@email> (raw)

Hello,
xen-3.4.3 x86_64, dom0 2.6.34-9.xenlinux as dom0,
2.6.32.14-1.2.105.pvops0 in PV domU. /proc/sys/xen/independent_wallclock is
0.
After resume from S3 sleep in dom0, the wall clock in domU is
desynchronized from dom0's one (the delta is the length of S3 sleep). It
does not seem that adj_timex is in progress (the delta is constant in time).

Is it a known issue ? If so, could someone point me to a solution ?
Regards,
Rafal Wojtczuk

             reply	other threads:[~2010-07-01  3:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01  3:04 Rafal Wojtczuk [this message]
2010-07-01 14:50 ` S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Keir Fraser
2010-07-01 14:51   ` Keir Fraser
2010-07-01 15:18   ` Joanna Rutkowska
2010-07-01 16:12     ` Keir Fraser
2010-07-05 19:18       ` Jeremy Fitzhardinge
2010-07-05 19:26         ` Keir Fraser
2010-07-05 22:43         ` Joanna Rutkowska
2010-07-05 22:50           ` Jeremy Fitzhardinge
2010-07-05 23:03             ` Joanna Rutkowska
2010-07-05 23:19               ` Jeremy Fitzhardinge
2010-07-06  9:12                 ` Joanna Rutkowska
2010-07-06 16:17                   ` Jeremy Fitzhardinge
2010-07-06  3:52             ` Keir Fraser
2010-07-06  9:10               ` Joanna Rutkowska
2010-07-06 10:02                 ` Jan Beulich
2010-07-06 10:27                   ` Joanna Rutkowska
2010-07-06 12:50                     ` Keir Fraser
2010-07-06 14:09                       ` Joanna Rutkowska
2010-07-08 14:06                         ` Joanna Rutkowska
2010-07-06 14:53                       ` Dan Magenheimer
2010-07-06 16:24                         ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100701030431.GB1431@email \
    --to=rafal@invisiblethingslab.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).