From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
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 11:09:40 -0400 [thread overview]
Message-ID: <20170524150940.GI18530@char.us.oracle.com> (raw)
In-Reply-To: <20170524142505.11460-1-olaf@aepfle.de>
On Wed, May 24, 2017 at 04:25:05PM +0200, Olaf Hering wrote:
> After migrating a domU to another identical host a performance drop can
> be observed. One reason is that before migration TSC was accessed at
> native speed, after migration TSC has to be emulated. This happens
> because the measured CPU frequency is not accurate, the values differ
> even between reboots.
>
> To avoid the emulation a tolerance range can be specified during boot
> with "vtsc-tolerance=N". If the frequency expected by the domU is
> within the range, TSC access from the domU will remain native. If the
How can that be determined? As in how can the guest (domU) be within
the range? Is there some way to determine that? Is there some
matrix of the various OS-es that can tolerate this?
_______________________________________________
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:09 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 [this message]
2017-05-24 15:25 ` Olaf Hering
2017-05-24 15:33 ` Konrad Rzeszutek Wilk
2017-05-24 15:44 ` Olaf Hering
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=20170524150940.GI18530@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=olaf@aepfle.de \
--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.