Re: [PATCH RFC] handle tsc_tolerance during migration between identical hosts

[Olaf Hering <olaf@aepfle.de>]

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

On Tue, Apr 18, Jan Beulich wrote:

> >>> On 18.04.17 at 11:50, <olaf@aepfle.de> wrote:
> > On Tue, Apr 11, Jan Beulich wrote:
> > 
> >> I'm afraid successful testing is not a sufficient criteria here. At
> >> the very least the (so far missing) documentation needs to very
> >> clearly point out the possible risks associated with using this
> >> option. But with there not being any functional change when
> >> the option is not being made use of, I don't think there's a
> >> reason not to add this (for the adventurous).
> > 
> > This can be handled by refering to the documentation of
> > 'tsc_mode=native', which is what this change actually does.
> 
> Does it? I've just looked at th patch again, and I didn't find any
> such referral. Are you perhaps talking about some change you
> only have done locally?

To me it looks like ->vtsc decides if there is emulation or not. So in
this sense tsc_mode remains "native" if the khz value is within the
tolerance range.


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