From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v12] tolerate jitter in cpu_khz calculation to avoid TSC emulation
Date: Mon, 11 Mar 2019 13:09:31 +0100 [thread overview]
Message-ID: <20190311130931.737ee8c6.olaf@aepfle.de> (raw)
In-Reply-To: <5C864446020000780021D29A@prv1-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
Am Mon, 11 Mar 2019 05:19:34 -0600
schrieb "Jan Beulich" <JBeulich@suse.com>:
> But of course the seemingly
> random 200 will itself need a much better reasoning, or at least a
> clear indication of the data base (number of different systems) that
> it was derived from. "Large number of hosts", after all, may mean 12
> to you and tens of thousands to me.
How many hosts would be relevant?
My own test hosts calibrate itself in a range of maybe 30 khz.
I gave up to track the exact numbers after every reboot.
If it helps, I can gather 'cpu_khz' once again.
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
next prev parent reply other threads:[~2019-03-11 12:09 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
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 [this message]
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=20190311130931.737ee8c6.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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.