From: "Jan Beulich" <JBeulich@suse.com>
To: Olaf Hering <olaf@aepfle.de>
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 01:25:07 -0600 [thread overview]
Message-ID: <592D3A73020000780015D790@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20170530063604.GA26792@aepfle.de>
>>> On 30.05.17 at 08:36, <olaf@aepfle.de> wrote:
> On Mon, May 29, Jan Beulich wrote:
>
>> Well, no, what jitter may be acceptable depends on the
>> applications running inside the guest. I.e. you can only know
>> for yourself or ask the application vendor(s). I think such an
>> option, if we really want to have it, would need to be
>> prominently documented as unsupported - after all we can't
>> help it if people use it and then find their applications break.
>
> The very same is true for tsc_mode=native, no such warning exists AFAIK.
I fully agree.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-30 7:25 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 [this message]
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=592D3A73020000780015D790@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.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.