From: Tianyu Lan <ltykernel@gmail.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Yubo Xie <yuboxie@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Tianyu Lan <Tianyu.Lan@microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, liuwe@microsoft.com,
daniel.lezcano@linaro.org, tglx@linutronix.de,
michael.h.kelley@microsoft.com
Subject: Re: [PATCH] x86/Hyper-V: Fix hv sched clock function return wrong time unit
Date: Wed, 25 Mar 2020 21:57:52 +0800 [thread overview]
Message-ID: <039e126f-f00d-d7e1-aa92-c049c9e3333b@gmail.com> (raw)
In-Reply-To: <87ftdx7nxv.fsf@vitty.brq.redhat.com>
Hi Vitaly:
Thanks for your review.
On 3/24/2020 11:49 PM, Vitaly Kuznetsov wrote:
> Yubo Xie <ltykernel@gmail.com> writes:
>
>> sched clock callback should return time with nano second as unit
>> but current hv callback returns time with 100ns. Fix it.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Yubo Xie <yuboxie@microsoft.com>
>> Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
>> Fixes: adb87ff4f96c ("clocksource/drivers/hyperv: Allocate Hyper-V TSC page statically")
>
> I don't think this is the right commit to reference,
>
> commit bd00cd52d5be655a2f217e2ed74b91a71cb2b14f
> Author: Tianyu Lan <Tianyu.Lan@microsoft.com>
> Date: Wed Aug 14 20:32:16 2019 +0800
>
> clocksource/drivers/hyperv: Add Hyper-V specific sched clock function
>
> looks like the one.
Sorry. You are right. Will update in the next version.
>
>> ---
>> drivers/clocksource/hyperv_timer.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/clocksource/hyperv_timer.c b/drivers/clocksource/hyperv_timer.c
>> index 9d808d595ca8..662ed978fa24 100644
>> --- a/drivers/clocksource/hyperv_timer.c
>> +++ b/drivers/clocksource/hyperv_timer.c
>> @@ -343,7 +343,8 @@ static u64 notrace read_hv_clock_tsc_cs(struct clocksource *arg)
>>
>> static u64 read_hv_sched_clock_tsc(void)
>> {
>> - return read_hv_clock_tsc() - hv_sched_clock_offset;
>> + return (read_hv_clock_tsc() - hv_sched_clock_offset)
>> + * (NSEC_PER_SEC / HV_CLOCK_HZ);
>> }
>>
>> static void suspend_hv_clock_tsc(struct clocksource *arg)
>> @@ -398,7 +399,8 @@ static u64 notrace read_hv_clock_msr_cs(struct clocksource *arg)
>>
>> static u64 read_hv_sched_clock_msr(void)
>> {
>> - return read_hv_clock_msr() - hv_sched_clock_offset;
>> + return (read_hv_clock_msr() - hv_sched_clock_offset)
>> + * (NSEC_PER_SEC / HV_CLOCK_HZ);
>> }
>
> kvmclock seems to have the same (pre-patch) code ...
kvm sched clock gets time from pvclock_clocksource_read() and
the time unit is nanosecond. So there is such issue in KVM code.
>
>>
>> static struct clocksource hyperv_cs_msr = {
>
next prev parent reply other threads:[~2020-03-25 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 15:19 Yubo Xie
2020-03-24 15:49 ` Vitaly Kuznetsov
2020-03-25 13:57 ` Tianyu Lan [this message]
2020-03-25 14:28 ` Vitaly Kuznetsov
2020-03-25 18:46 ` Dexuan Cui
2020-03-25 18:57 ` Yubo Xie
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=039e126f-f00d-d7e1-aa92-c049c9e3333b@gmail.com \
--to=ltykernel@gmail.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=daniel.lezcano@linaro.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwe@microsoft.com \
--cc=michael.h.kelley@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=yuboxie@microsoft.com \
/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
all inboxes | Powered by JetHome®