From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: elena.ufimtseva@oracle.com
Cc: keir@xen.org, jbeulich@suse.com, tim@xen.org,
xen-devel@lists.xen.org, Aravind.Gopalakrishnan@amd.com,
suravee.suthikulpanit@amd.com, boris.ostrovsky@oracle.com,
Mukesh Rathor <mukesh.rathor@oracle.com>,
roger.pau@citrix.com
Subject: Re: [PATCH 5/6] AMD-PVH: Support TSC_MODE_NEVER_EMULATE for PVH
Date: Mon, 22 Jun 2015 13:12:59 -0400 [thread overview]
Message-ID: <20150622171259.GF5408@l.oracle.com> (raw)
In-Reply-To: <1434991058-6585-6-git-send-email-elena.ufimtseva@oracle.com>
On Mon, Jun 22, 2015 at 12:37:37PM -0400, elena.ufimtseva@oracle.com wrote:
> From: Elena Ufimtseva <elena.ufimtseva@oracle.com>
>
> On AMD, MSR_AMD64_TSC_RATIO must be set for rdtsc instruction in guest
> to properly read the cpu tsc. To that end, set tsc_khz in struct domain.
It looks like the TSC_MODE_DEFAULT, TSC_MODE_ALWAYS_EMULATE, and
TSC_MODE_PVRDTSCP already set tsc_khz.
Only TSC_MODE_NEVER_EMULATE hadn't set it (but that
piece of code has some continuation from TSC_MODE_DEFAULT).
And we need this otherwise the CPU tsc offset has bogus data?
Anyway if this is the way to go, you can probably delete:
1968 d->arch.tsc_khz = cpu_khz;
>
> Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
> ---
> xen/arch/x86/time.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/xen/arch/x86/time.c b/xen/arch/x86/time.c
> index bbb7e6c..d9709ce 100644
> --- a/xen/arch/x86/time.c
> +++ b/xen/arch/x86/time.c
> @@ -1923,6 +1923,7 @@ void tsc_set_info(struct domain *d,
> * but "always_emulate" does not for some reason. Figure out
> * why.
> */
> + d->arch.tsc_khz = cpu_khz;
> switch ( tsc_mode )
> {
> case TSC_MODE_NEVER_EMULATE:
> --
> 1.9.3
>
next prev parent reply other threads:[~2015-06-22 17:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 16:37 [PATCH 0/6] AMD-PVH: DomU support elena.ufimtseva
2015-06-22 16:37 ` [PATCH 1/6] pvh: domu construct vmcb 64 bit mode start elena.ufimtseva
2015-06-22 19:00 ` Boris Ostrovsky
2015-06-23 12:02 ` Jan Beulich
2015-06-24 20:15 ` Elena Ufimtseva
2015-06-25 8:06 ` Jan Beulich
2015-06-24 20:18 ` Elena Ufimtseva
2015-06-22 16:37 ` [PATCH 2/6] AMD-PVH: cpuid intercept elena.ufimtseva
2015-06-23 12:09 ` Jan Beulich
2015-06-22 16:37 ` [PATCH 3/6] AMD-PVH: call hvm_emulate_one instead of handle_mmio elena.ufimtseva
2015-06-22 19:29 ` Boris Ostrovsky
2015-06-23 12:12 ` Jan Beulich
2015-06-22 16:37 ` [PATCH 4/6] AMD-PVH: Do not get/set vlapic TPR elena.ufimtseva
2015-06-23 12:17 ` Jan Beulich
2015-06-22 16:37 ` [PATCH 5/6] AMD-PVH: Support TSC_MODE_NEVER_EMULATE for PVH elena.ufimtseva
2015-06-22 17:12 ` Konrad Rzeszutek Wilk [this message]
2015-06-23 12:23 ` Jan Beulich
2015-06-22 16:37 ` [PATCH 6/6] AMD-PVH: enable pvh if requirements met elena.ufimtseva
2015-06-23 12:30 ` Jan Beulich
2015-06-24 2:34 ` Boris Ostrovsky
2015-06-24 7:49 ` Jan Beulich
2015-06-24 18:24 ` Andrew Cooper
2015-06-24 20:26 ` Elena Ufimtseva
2015-06-24 21:41 ` Mukesh Rathor
2015-06-25 14:11 ` Elena Ufimtseva
2015-06-23 11:58 ` [PATCH 0/6] AMD-PVH: DomU support 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=20150622171259.GF5408@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=mukesh.rathor@oracle.com \
--cc=roger.pau@citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--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.