From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: time does not move forward in HVM guests
Date: Tue, 4 Jul 2017 18:34:09 +0200 [thread overview]
Message-ID: <20170704163326.GA22633@aepfle.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
In my testing with sysbench in a HVM domU running a linux-4.4 based
pvops kernel on a xen-4.7 based dom0 the time does not move forward
properly:
There (URL below) is basically code like this:
clock_gettime(CLOCK_MONOTONIC, a)
do_work
clock_gettime(CLOCK_MONOTONIC, b)
diff_time(a,b)
All 'do_work' does is writing zeros to a block of memory.
clock_getres(CLOCK_MONOTONIC) indicates a resolution of 1ns.
If 'do_work' takes like 100ns or less: a==b. I think this is something
that should not happen. In case of vcpu overcommit this happens also
when 'do_work' takes around 800ns. At some point I have also seen cases
of time going backward. I can not reproduce this anymore, might have
been bugs in my code or the domU.cfg changed.
A workaround is booting the domU kernel with 'clocksource=tsc nohz=off highres=off'.
Why does this happen? Are the expectations too high?
Olaf
https://github.com/olafhering/sysbench/compare/master...pv
bash autogen.sh
make -j
bash mem.1K.on.sh
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-07-04 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 16:34 Olaf Hering [this message]
2017-07-05 6:58 ` time does not move forward in HVM guests Jan Beulich
2017-07-05 7:25 ` Olaf Hering
2017-07-05 8:14 ` Jan Beulich
2017-07-05 8:51 ` Olaf Hering
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=20170704163326.GA22633@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.