All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v13] tolerate jitter in cpu_khz calculation to avoid TSC emulation
Date: Wed, 13 Mar 2019 14:35:41 +0100	[thread overview]
Message-ID: <20190313143541.6a008762.olaf@aepfle.de> (raw)
In-Reply-To: <5C88DD8E020000780021E0A6@prv1-mh.provo.novell.com>


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

Am Wed, 13 Mar 2019 04:38:06 -0600
schrieb "Jan Beulich" <JBeulich@suse.com>:

> But this affects a guest even ahead of migration. What if one
> uses migration really just for emergencies? Why would they
> run their guests in always-emulate mode?

Because this is what they will end up for the lifetime of the domU after migration?
The domU can not be just migrated back in the hope the originating
host has the expected cpu_khz value.

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

  reply	other threads:[~2019-03-13 13:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  8:28 [PATCH v13] tolerate jitter in cpu_khz calculation to avoid TSC emulation Olaf Hering
2019-03-13  9:18 ` Jan Beulich
2019-03-13 10:23   ` Olaf Hering
2019-03-13 10:38     ` Jan Beulich
2019-03-13 13:35       ` Olaf Hering [this message]
2019-03-13 14:30         ` Jan Beulich
2019-03-13 13:51   ` Olaf Hering
2019-03-13 14:36     ` Jan Beulich
2019-03-13 16:02       ` Olaf Hering
2019-03-14 11:58   ` Olaf Hering
2019-03-14 13:50   ` Olaf Hering
2019-03-14 14:10     ` Juergen Gross
2019-03-14 14:14       ` Olaf Hering
2019-03-14 14:24         ` Juergen Gross
2019-03-14 14:33           ` Olaf Hering
2019-03-14 14:36             ` Jan Beulich
2019-03-14 14:41               ` Olaf Hering
2019-03-19 14:20                 ` Olaf Hering
2019-03-14 14:38             ` Juergen Gross
2019-03-14 14:46               ` Olaf Hering
2019-03-14 15:03                 ` Juergen Gross
2019-03-14 14:20     ` Jan Beulich
2019-03-14 14:27       ` 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=20190313143541.6a008762.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --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.