All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xenproject.org
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Wei Liu" <wei.liu2@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v12] tolerate jitter in cpu_khz calculation to avoid TSC emulation
Date: Fri, 8 Mar 2019 20:29:07 +0100	[thread overview]
Message-ID: <20190308202907.56f7609a.olaf@aepfle.de> (raw)
In-Reply-To: <20190308192059.24610-1-olaf@aepfle.de>


[-- Attachment #1.1: Type: text/plain, Size: 515 bytes --]

Am Fri,  8 Mar 2019 20:20:59 +0100
schrieb Olaf Hering <olaf@aepfle.de>:

> To reiterate the second paragraph: if a domU uses TSC as primary clock
> source, it is expected that it runs NTP to cover for the resulting
> drift. Therefore this change does no need a knob to turn it on or off.

One interesting aspect is: the xenlinux based kernels report clocksource=tsc,
but I think there was no explicit requirement to run NTP in domU.
There was even that 'independent_wallclock' knob. Why is that?

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-03-08 19:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 19:20 [PATCH v12] tolerate jitter in cpu_khz calculation to avoid TSC emulation Olaf Hering
2019-03-08 19:29 ` Olaf Hering [this message]
2019-03-11 10:02   ` Jan Beulich
2019-03-11 10:26     ` Olaf Hering
2019-03-11 10:42       ` Jan Beulich
2019-03-11 10:16 ` Jan Beulich
2019-03-11 10:49   ` Olaf Hering
2019-03-11 11:19     ` Jan Beulich
2019-03-11 11:57       ` Olaf Hering
2019-03-11 14:07         ` Jan Beulich
2019-03-11 12:09       ` Olaf Hering
2019-03-11 14:11         ` Jan Beulich
2019-03-12 10:03   ` 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=20190308202907.56f7609a.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.