Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4055426ybl; Mon, 26 Aug 2019 04:56:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqwK+6drzzAchmeGR7wiyrZXXsr05R4MB4tw7yx3H2iuyEZuPKLsoIIEYk5ncr3zt43ahou9 X-Received: by 2002:a65:6713:: with SMTP id u19mr15086631pgf.403.1566820594998; Mon, 26 Aug 2019 04:56:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566820594; cv=none; d=google.com; s=arc-20160816; b=xzrBz8S6AU23fDN9oQD3z37Klk5Tp8skwzvDZXIN10nUDJt0mi1K56vKGV4bcOJJ4T JYeeCg6FAka0LBC+CO7g6jPKdOO3RCG0Xoh82Yuf6lwMhygivW/hkjBweSlymA38rh6q HEaA00WhU1C2YeDRdxhu2X7XuMPw04QmOJDWX+9P8bZ4AKsvIbOKY1vpbT1sGYy9KsBv WBKVS5stikLUDl4XPVaDwRPJ0r4pzOAuMtiSsZkZh31iCfLJbx7Yhx9VwanTKqNCvboK TrBAjZj/dZeTZ6Q71+qCSmXm9XS+pzp3fJL1edNrUCDe97337SkVdwp0XCN757Fa7snD BETA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=BuKOkwXyfRdC/DpNbQQBPM6WYSLV6PyrdbNsCZtB09k=; b=EZu2t6J6wQFpaemV1/dG9WvW30L5O8wYY/wgW4cXqTeeV6GG08Buq0AJsWBuW6IRTb f3i6GZMw7ZVVt7Ft6kx8/9tG02Ogisx9iO03Fx21PET4F17aDTI4QQCJyqueS3n+lcok y1xE4S1CHrOyQ98XBNUGUQMe3A2zeBMM6Iv2eAo0BOEiztizHPvfj33wGXQZheLgiyZ9 4d5587m+9awCIhY1TNyInOb5bPdaLxr1SkPZa0a/5HfnEptqc1IMr6aM1s+beA9JLUfI 5iFnsWwkTW9LGy128GGMwWLICmXaErzLbZoAT0xCe7chMWiNW5e4dxb05NcdUZOPo5qn hhnQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j6si8722392pgb.206.2019.08.26.04.56.19; Mon, 26 Aug 2019 04:56:34 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731188AbfHZLzK (ORCPT + 99 others); Mon, 26 Aug 2019 07:55:10 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:39649 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727182AbfHZLzK (ORCPT ); Mon, 26 Aug 2019 07:55:10 -0400 Received: from p5de0b6c5.dip0.t-ipconnect.de ([93.224.182.197] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1i2DaU-0001LY-NS; Mon, 26 Aug 2019 13:55:06 +0200 Date: Mon, 26 Aug 2019 13:55:05 +0200 (CEST) From: Thomas Gleixner To: Vitaly Kuznetsov cc: Sasha Levin , lantianyu1986@gmail.com, Tianyu Lan , linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org, daniel.lezcano@linaro.org, michael.h.kelley@microsoft.com Subject: Re: [PATCH] x86/Hyper-V: Fix build error with CONFIG_HYPERV_TSCPAGE=N In-Reply-To: <87d0gso0jf.fsf@vitty.brq.redhat.com> Message-ID: References: <20190822053852.239309-1-Tianyu.Lan@microsoft.com> <87zhk1pp9p.fsf@vitty.brq.redhat.com> <20190824151218.GM1581@sasha-vm> <87d0gso0jf.fsf@vitty.brq.redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Aug 2019, Vitaly Kuznetsov wrote: > Sasha Levin writes: > > > On Thu, Aug 22, 2019 at 10:39:46AM +0200, Vitaly Kuznetsov wrote: > >>lantianyu1986@gmail.com writes: > >> > >>> From: Tianyu Lan > >>> > >>> Both Hyper-V tsc page and Hyper-V tsc MSR code use variable > >>> hv_sched_clock_offset for their sched clock callback and so > >>> define the variable regardless of CONFIG_HYPERV_TSCPAGE setting. > >> > >>CONFIG_HYPERV_TSCPAGE is gone after my "x86/hyper-v: enable TSC page > >>clocksource on 32bit" patch. Do we still have an issue to fix? > > > > Yes. Let's get it fixed on older kernels (as such we need to tag this > > one for stable). The 32bit TSC patch won't come in before 5.4 anyway. > > > > Vitaly, does can you ack this patch? It might require you to re-spin > > your patch. > > > > Sure, no problem, > > Acked-by: Vitaly Kuznetsov > > I, however, was under the impression the patch fixes the issue with the > newly introduced sched clock: > > commit b74e1d61dbc614ff35ef3ad9267c61ed06b09051 > Author: Tianyu Lan > Date: Wed Aug 14 20:32:16 2019 +0800 > > clocksource/hyperv: Add Hyper-V specific sched clock function > > (and Fixes: tag is missing) > > and this is not in mainline as of v5.3-rc6. In tip/timers/core Thomas > already picked my "clocksource/drivers/hyperv: Enable TSC page > clocksource on 32bit" which also resolves the issue. No. I folded Sashas fix into the original clocksource patch and then added yours on top. Thanks, tglx