From: Thomas Gleixner <tglx@linutronix.de>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Stephen Hemminger <sthemmin@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
devel@linuxdriverproject.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method
Date: Fri, 10 Feb 2017 12:15:03 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702101214540.4036@nanos> (raw)
In-Reply-To: <87lgteqp88.fsf@vitty.brq.redhat.com>
On Fri, 10 Feb 2017, Vitaly Kuznetsov wrote:
> Thomas Gleixner <tglx@linutronix.de> writes:
>
> > On Thu, 9 Feb 2017, Vitaly Kuznetsov wrote:
> >> +#ifdef CONFIG_HYPERV_TSCPAGE
> >> +static notrace u64 vread_hvclock(int *mode)
> >> +{
> >> + const struct ms_hyperv_tsc_page *tsc_pg =
> >> + (const struct ms_hyperv_tsc_page *)&hvclock_page;
> >> + u64 sequence, scale, offset, current_tick, cur_tsc;
> >> +
> >> + while (1) {
> >> + sequence = READ_ONCE(tsc_pg->tsc_sequence);
> >> + if (!sequence)
> >> + break;
> >> +
> >> + scale = READ_ONCE(tsc_pg->tsc_scale);
> >> + offset = READ_ONCE(tsc_pg->tsc_offset);
> >> + rdtscll(cur_tsc);
> >> +
> >> + current_tick = mul_u64_u64_shr(cur_tsc, scale, 64) + offset;
> >> +
> >> + if (READ_ONCE(tsc_pg->tsc_sequence) == sequence)
> >> + return current_tick;
> >
> > That sequence stuff lacks still a sensible explanation. It's fundamentally
> > different from the sequence counting we do in the kernel, so documentation
> > for it is really required.
>
> Sure, do you think the following would do?
Yes
> diff --git a/arch/x86/entry/vdso/vclock_gettime.c b/arch/x86/entry/vdso/vclock_gettime.c
> index 4af10b4..886b600 100644
> --- a/arch/x86/entry/vdso/vclock_gettime.c
> +++ b/arch/x86/entry/vdso/vclock_gettime.c
> @@ -154,6 +154,22 @@ static notrace u64 vread_hvclock(int *mode)
> (const struct ms_hyperv_tsc_page *)&hvclock_page;
> u64 sequence, scale, offset, current_tick, cur_tsc;
>
> + /*
> + * The protocol for reading Hyper-V TSC page is specified in Hypervisor
> + * Top-Level Functional Specification ver. 3.0 and above. To get the
> + * reference time we must do the following:
> + * - READ ReferenceTscSequence
> + * A special '0' value indicates the time source is unreliable and we
> + * need to use something else. The currently published specification
> + * versions (up to 4.0b) contain a mistake and wrongly claim '-1'
> + * instead of '0' as the special value, see commit c35b82ef0294.
> + * - ReferenceTime =
> + * ((RDTSC() * ReferenceTscScale) >> 64) + ReferenceTscOffset
> + * - READ ReferenceTscSequence again. In case its value has changed
> + * since our first reading we need to discard ReferenceTime and repeat
> + * the whole sequence as the hypervisor was updating the page in
> + * between.
> + */
> while (1) {
> sequence = READ_ONCE(tsc_pg->tsc_sequence);
> if (!sequence)
>
> --
> Vitaly
>
next prev parent reply other threads:[~2017-02-10 11:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170209141052.18694-1-vkuznets@redhat.com>
2017-02-09 14:10 ` [PATCH 1/2] hyperv: implement hv_get_tsc_page() Vitaly Kuznetsov
2017-02-09 14:10 ` [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method Vitaly Kuznetsov
[not found] ` <20170209141052.18694-3-vkuznets@redhat.com>
2017-02-09 17:08 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.20.1702091806400.3604@nanos>
2017-02-09 18:27 ` Stephen Hemminger via Virtualization
2017-02-10 12:25 ` Vitaly Kuznetsov
2017-02-10 12:28 ` Thomas Gleixner
2017-02-10 16:31 ` Stephen Hemminger via Virtualization
[not found] ` <BLUPR0301MB2098E1283D42BD2C3772D839CC440@BLUPR0301MB2098.namprd03.prod.outlook.com>
2017-02-10 18:01 ` Thomas Gleixner
2017-02-13 7:49 ` Dexuan Cui via Virtualization
2017-02-13 9:27 ` Thomas Gleixner
2017-02-13 19:06 ` Andy Lutomirski
2017-02-13 19:28 ` Thomas Gleixner
2017-02-09 20:45 ` KY Srinivasan via Virtualization
[not found] ` <DM5PR03MB24903D71121176FFAED30E33A0450@DM5PR03MB2490.namprd03.prod.outlook.com>
2017-02-09 22:55 ` Andy Lutomirski
2017-02-09 23:15 ` Stephen Hemminger
2017-02-10 12:15 ` Vitaly Kuznetsov
2017-02-10 11:06 ` Vitaly Kuznetsov
2017-02-10 11:15 ` Thomas Gleixner [this message]
[not found] ` <20170209141052.18694-2-vkuznets@redhat.com>
2017-02-09 18:24 ` [PATCH 1/2] hyperv: implement hv_get_tsc_page() Stephen Hemminger via Virtualization
2017-02-09 20:14 ` Thomas Gleixner
2017-02-09 23:17 ` Stephen Hemminger
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=alpine.DEB.2.20.1702101214540.4036@nanos \
--to=tglx@linutronix.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.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