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>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: preserve native TSC speed during migration between identical hosts
Date: Tue, 30 May 2017 08:41:08 +0200 [thread overview]
Message-ID: <20170530064108.GB26792@aepfle.de> (raw)
In-Reply-To: <592C514F020000780015D542@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 545 bytes --]
On Mon, May 29, Jan Beulich wrote:
> Finally I don't think a host wide option will do. If it is to be of use
> (considering that it used wrong may break applications), it needs
> to be per-domain, and its value needs to be migrated (perhaps
> in the form of a low/high pair of TSC frequency values).
How is it supposed to be propagated from one host to another?
With the global option one can unconditionally receive a domU and
preserve "native performance" in case of tsc_mode=default. With a
per-domU option one has to know upfront.
Olaf
[-- 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 prev parent reply other threads:[~2017-05-30 6:41 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
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 [this message]
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=20170530064108.GB26792@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.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.