xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: preparations for 4.4.1, 4.3.3, and 4.2.5
Date: Tue, 20 May 2014 09:31:46 -0400	[thread overview]
Message-ID: <537B5942.4050302@oracle.com> (raw)
In-Reply-To: <537B6685020000780001414A@mail.emea.novell.com>

On 05/20/2014 08:28 AM, Jan Beulich wrote:
>>>> On 19.05.14 at 22:14, <boris.ostrovsky@oracle.com> wrote:
>> Hypervisor:
>> 88e64cb x86/HVM: use fixed TSC value when saving or restoring domain
>> b95fd03 x86/svm: enable TSC scaling
>> 82713ec x86: use native RDTSC(P) execution when guest and host
>> frequencies are the same
> My understanding was that these are solely about performance,
> not correctness. That would make them weak candidates for
> 4.4.1 (under the slightly relaxed rules we put on x.y.1 releases),
> but not any of the older trees. Do you have a different view?

No, these are correctness fixes.

The main thing (in this context) about 82713ec is reverting part of 
4aab59a3 which broke migration on SVM (in principle I think you can take 
only the first hunk from it)

88e64cb fixes the fact that TSCs get unsynchronized after migration. And 
it needs some of the interfaces introduced in b95fd03 (which in itself 
is indeed mostly about performance)

-boris

  reply	other threads:[~2014-05-20 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5379E20E02000078000136E7@mail.emea.novell.com>
2014-05-19 14:12 ` preparations for 4.4.1, 4.3.3, and 4.2.5 Jan Beulich
2014-05-19 14:23   ` Andrew Cooper
2014-05-19 14:30     ` Ian Jackson
2014-05-19 20:14   ` Boris Ostrovsky
2014-05-20 12:28     ` Jan Beulich
2014-05-20 13:31       ` Boris Ostrovsky [this message]
2014-05-23 13:47         ` Jan Beulich
2014-05-21 15:03   ` Daniel Kiper
2014-05-21 15:12     ` Jan Beulich
2014-05-30 12:03       ` Daniel Kiper
2014-06-11 19:28         ` Daniel Kiper
2014-10-07 10:04           ` Daniel Kiper
2014-05-27  7:44   ` Olaf Hering
2014-05-27  8:23     ` Olaf Hering
2014-05-27  9:23     ` Jan Beulich
2014-06-25 10:29   ` Roger Pau Monné
2014-06-25 10:34     ` Roger Pau Monné
2014-06-25 10:37     ` 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=537B5942.4050302@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).