From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org, Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH] xen: preserve native TSC speed during migration between identical hosts
Date: Wed, 24 May 2017 17:44:56 +0200 [thread overview]
Message-ID: <20170524174456.69b45ff6.olaf@aepfle.de> (raw)
In-Reply-To: <20170524153315.GO18530@char.us.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]
Am Wed, 24 May 2017 11:33:15 -0400
schrieb Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> But it does not help customers to figure out if this is OK for them?
> As in, how can customers be assured that 1% jitter is OK for their
> kernel? That time won't go backwards?
Well, that would be some new documentation.
I think the tsc_mode=native part already lacks that info.
In my testing time does not go backwards. The actual value of tsc
is different anyway on each host. Querying an ntp server shows no
drift, the offset remains within the +- 0.5 sec range.
> Is there some form of tests that they can run to verify and test
> that this is safe? Or perhaps this is something that is based on the kernel
> versions? Like 4.11 are safe, but 3.18 is not?
I'm not aware of any tests to measure the results of such jitter
with tsc_mode=native.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- 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 prev parent reply other threads:[~2017-05-24 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 14:25 [PATCH] xen: preserve native TSC speed during migration between identical hosts Olaf Hering
2017-05-24 15:09 ` Konrad Rzeszutek Wilk
2017-05-24 15:25 ` Olaf Hering
2017-05-24 15:33 ` Konrad Rzeszutek Wilk
2017-05-24 15:44 ` Olaf Hering [this message]
2017-05-29 14:45 ` Jan Beulich
2017-05-30 6:36 ` Olaf Hering
2017-05-30 7:25 ` Jan Beulich
2017-05-30 9:27 ` Olaf Hering
2017-05-30 14:28 ` Konrad Rzeszutek Wilk
2017-05-29 14:50 ` Jan Beulich
2017-05-30 6:41 ` Olaf Hering
2017-05-30 7:27 ` Jan Beulich
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=20170524174456.69b45ff6.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--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.