Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4984910ybb; Tue, 24 Mar 2020 08:51:39 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvKy8o7qmv0o+4RGZKTZhkHNgGnymbhvPZcrmx5ilvomFuMZJUQfPNsyswD0jYUr1Ea8z1d X-Received: by 2002:a05:6830:15d5:: with SMTP id j21mr6392348otr.346.1585065099355; Tue, 24 Mar 2020 08:51:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585065099; cv=none; d=google.com; s=arc-20160816; b=eeRt9lvbGMNq9j/GY5zMvoXHo6i+a3/5TjV2a4LDQSFMjgu+eT7o4Y9QS8KmQf6sMP vdBL/2D5b7x6/fWgARAmTM3b3KCfx2vvvdwm/ukScrsgQWJPWWnAnRnLj2ECHL2miM3E kojF6WftHderCF97ZaOZTYYhjZMB3a87W7/TGaqqu5QZ6+g42hCLtJmnk4kiwWiGuhn7 /0m/jy9t558VUYJhyRllDspOHf3apCCj2vLt4iBEpa3BuJR1Bhy8v7j54+CRTbFvDP39 noxLD8Y2VNbwJJca0JeKTxNVngWx0Mm7npjnfarWG0b+EnjrZVzSX9vXaqzOABH9sNxm uyWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=gDeYcAUSbBq7ywkS5vACQpnT9b7hAluwSzLUAQ2Mkuo=; b=V95d8yecEiF+IKiXZBXVJFqMZeX+burFHLuNyZngVV9/2fLjdfEp3NUu7lUNk4l8OZ ulNltipDfvnThC7mhJuHJh+jWS4lomh6/wpiRIloQVx+i3IB4woI2z3gZkePVWK9xHYt n3hJN1QOGr4Ome8A1jTLBV6JLnYCwWsJCuqPj8KAOa13WU6QMUVEn/N6Lizdc/v1+HjQ WMSXZEVuE0WYBnEIL7CBSYcEN0eEMNv9gKX1hH4yMXcI1sY6CWc2jVybuLlTnY1E9hpR oGsUlrezLPprkVsjurqb53p1USCatlP46sQ2XdXnTBdWtxrMK1ldFJ92wBi1OSVxzdd5 ID/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UWyq109a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l4si1703514otf.195.2020.03.24.08.51.26; Tue, 24 Mar 2020 08:51:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UWyq109a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728660AbgCXPtl (ORCPT + 99 others); Tue, 24 Mar 2020 11:49:41 -0400 Received: from us-smtp-delivery-74.mimecast.com ([216.205.24.74]:40486 "EHLO us-smtp-delivery-74.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728555AbgCXPtk (ORCPT ); Tue, 24 Mar 2020 11:49:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585064979; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gDeYcAUSbBq7ywkS5vACQpnT9b7hAluwSzLUAQ2Mkuo=; b=UWyq109aARiETWzOJF2nSEcrF78b/fpxAMDOEblWVBaKVZRkAvuh9FgICyU5P3OL/PIKGY d2aZaLMp4lkQ5L64NdKbuj0fWXA6ZBciuJaAV+xpFr2fcWLCSghBhfH7GDI19QyqB3ykfW 1mu6ajt+nzYY4jbimbsOy67zr+Yg5gg= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-105-4OmS1QYJMHWRFLqq5-9pww-1; Tue, 24 Mar 2020 11:49:35 -0400 X-MC-Unique: 4OmS1QYJMHWRFLqq5-9pww-1 Received: by mail-wr1-f71.google.com with SMTP id v14so832991wrq.13 for ; Tue, 24 Mar 2020 08:49:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=gDeYcAUSbBq7ywkS5vACQpnT9b7hAluwSzLUAQ2Mkuo=; b=G7WvxHCugCULHpN+LIlmvx83GsQe78BnHSkX3FRgOqv4AGGMx9AT6Acef6rdjJD6lu gFD5jwc8cjhRkWjIX2vbaEbNPgxqGR/4+azuuDp1OydL88+722ZOnIcaL0IalUbGVDVl 4KiYpouFTtblX8TM7JW33HX77OgBrDmAKCZLRz6+s/eBYwISQbhp154Ugmz+oYBjchCQ 9p00o4SLYsY0VPjfgQuCZ/PMgMAuzmBe6souzPcw8kao/07jBUD/C+VIN/pimMVUaVTo 6lNh8IdyBMXnHJtiqRaT0j64vPSZYyf7mko4Pe6KyvqESw2Rn2E3YnK78x6U4nadsOeU trnA== X-Gm-Message-State: ANhLgQ0dauKL8cmQ78KKa65t0YAZcKdO6/0xnf2lwo5M1ZyHLeEqAPcK PL/1AIz28M/IEruE2c0cA4Arrv+pmd7m7hoMpSmyJkFj4IbP6k6B4LzBBmFs410URTTjrvyK9tS yNxlQP+7THGu+QYAxdXssPH8t X-Received: by 2002:adf:ce8d:: with SMTP id r13mr21284978wrn.253.1585064974714; Tue, 24 Mar 2020 08:49:34 -0700 (PDT) X-Received: by 2002:adf:ce8d:: with SMTP id r13mr21284953wrn.253.1585064974406; Tue, 24 Mar 2020 08:49:34 -0700 (PDT) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id y7sm6862882wrq.54.2020.03.24.08.49.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Mar 2020 08:49:33 -0700 (PDT) From: Vitaly Kuznetsov To: Yubo Xie Cc: Yubo Xie , linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Tianyu Lan , 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 In-Reply-To: <20200324151935.15814-1-yuboxie@microsoft.com> References: <20200324151935.15814-1-yuboxie@microsoft.com> Date: Tue, 24 Mar 2020 16:49:32 +0100 Message-ID: <87ftdx7nxv.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Yubo Xie 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 > Signed-off-by: Tianyu Lan > 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 Date: Wed Aug 14 20:32:16 2019 +0800 clocksource/drivers/hyperv: Add Hyper-V specific sched clock function looks like the one. > --- > 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 ... > > static struct clocksource hyperv_cs_msr = { -- Vitaly