From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, suravee.suthikulpanit@amd.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
jun.nakajima@intel.com
Subject: Re: [PATCH v4 1/3] x86: Use native RDTSC(P) execution when guest and host frequencies are the same
Date: Wed, 16 Apr 2014 12:44:02 -0400 [thread overview]
Message-ID: <534EB352.2000207@oracle.com> (raw)
In-Reply-To: <534EC8C50200007800009B44@nat28.tlf.novell.com>
On 04/16/2014 12:15 PM, Jan Beulich wrote:
> Please sort this out with Mukesh - I would generally have thought that
> time handling should be HVM-like for PVH, and was surprised (in the
> sense that I didn't recall) to find that fixme comment there when
> reviewing your patch.
Do you want PVH issues be resolved in this series or separately?
-boris
>
>> PVH need to be looked at anyway. For example, there is a is_hvm_domain()
>> check at the bottom which I suspect needs to be PVH-safe.
> Indeed this all looks rather suspicious...
>
> Jan
>
next prev parent reply other threads:[~2014-04-16 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 1:27 [PATCH v4 0/3] Time-related fixes for migration Boris Ostrovsky
2014-04-16 1:27 ` [PATCH v4 1/3] x86: Use native RDTSC(P) execution when guest and host frequencies are the same Boris Ostrovsky
2014-04-16 9:54 ` Jan Beulich
2014-04-16 13:02 ` Boris Ostrovsky
2014-04-16 11:38 ` Jan Beulich
2014-04-16 14:28 ` Boris Ostrovsky
2014-04-16 14:37 ` Jan Beulich
2014-04-16 15:33 ` Boris Ostrovsky
2014-04-16 16:15 ` Jan Beulich
2014-04-16 16:44 ` Boris Ostrovsky [this message]
2014-04-17 6:29 ` Jan Beulich
2014-04-16 1:27 ` [PATCH v4 2/3] x86/svn: Enable TSC scaling Boris Ostrovsky
2014-04-16 10:21 ` Jan Beulich
2014-04-16 10:53 ` Andrew Cooper
2014-04-16 1:27 ` [PATCH v4 3/3] x86/HVM: Use fixed TSC value when saving or restoring domain Boris Ostrovsky
2014-04-16 10:22 ` 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=534EB352.2000207@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=suravee.suthikulpanit@amd.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.