Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp491994ybd; Sat, 22 Jun 2019 07:47:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqwiJ4gSzR8gBnKBkCKJpyLvf5Y4A4oHp9FHVroIUNtss6LX4EmoU7BLHEapQ7YXLeSF6HZY X-Received: by 2002:a17:90a:db42:: with SMTP id u2mr13565262pjx.48.1561214834130; Sat, 22 Jun 2019 07:47:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561214834; cv=none; d=google.com; s=arc-20160816; b=ZdPW3DuJ3Q5AAXJI3RgBZzLydJyMSKorn47r6n+ycMaO/6U7PqRpYtw1rNQ9jYUjdJ gj7f56SCNqDilaoNZUvxmTEJA7DzjAj2iBi/RCUpS8++LYZzubBtJG1mFBc4GtqkNUtP 3NddzHM7GCVTICLCfMqXaVzLhq/Z8xsNhR2pCWA+iHxb3Yh0OeZv1AfcQLefTpjffg0H Vjv/DUJ7wejRbaJzSM6pq0yfFVW51aGWxW8HF4psKlBaEBrq0b0J39l0svcgyv3aGnDA 37C4N1IEZfeCEtjHgP1wlIabaqx3TdxUHqw8Myo7xsh3flHRvYc0BmqRV2UNz4WRV9SW yaHQ== 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=M4aw8KfvAj9j6qSIwGW6Ue6a2YL3EIP5L9MLMOfiB/I=; b=OOUKVCBtbzgZd4NPIBlnleWRILVvK4JAPH6saJXCY7+dKVw4l0zbEK+Y+TBihylZQU feeyf7hgPpyPj6FjEHrdGXSueprXOLcaI4zIhkt4C9PdUk9O/aXww/PNwS6pE7EB4Aj2 Y1mfhU38fxC6B4QzqA57P67gJHnDH7EzIKYsHBGLHVGUlpxZdznuequ79Nnw8Xku8Ark 3OKuGEQ888nRnbqYKJKlk3sLspQ3poORfhpfXbl1G6tMdLyCoq1nve3OsU/0+0Xf5BSp AQTJCgZ59q74avWg0HG1Ih/VjhDlFL8L+Yv/0Xb2MyG2+fb/AsGEsyBKIwyIGNbHbC6e Tdjw== 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 b139si5451307pfb.38.2019.06.22.07.46.58; Sat, 22 Jun 2019 07:47:14 -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 S1726334AbfFVOqy (ORCPT + 99 others); Sat, 22 Jun 2019 10:46:54 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:57888 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726138AbfFVOqy (ORCPT ); Sat, 22 Jun 2019 10:46:54 -0400 Received: from p5b06daab.dip0.t-ipconnect.de ([91.6.218.171] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hehHh-00084j-Nz; Sat, 22 Jun 2019 16:46:30 +0200 Date: Sat, 22 Jun 2019 16:46:28 +0200 (CEST) From: Thomas Gleixner To: Sasha Levin cc: Michael Kelley , Vincenzo Frascino , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-mips@vger.kernel.org" , "linux-kselftest@vger.kernel.org" , Catalin Marinas , Will Deacon , Arnd Bergmann , Russell King , Ralf Baechle , Paul Burton , Daniel Lezcano , Mark Salyzyn , Peter Collingbourne , Shuah Khan , Dmitry Safonov <0x7f454c46@gmail.com>, Rasmus Villemoes , Huw Davies , linux-hyperv@vger.kernel.org, Greg KH , Stephen Rothwell Subject: Re: [PATCH v6 18/19] x86: Add support for generic vDSO In-Reply-To: <20190614211710.GQ1513@sasha-vm> Message-ID: References: <20190530141531.43462-1-vincenzo.frascino@arm.com> <20190530141531.43462-19-vincenzo.frascino@arm.com> <20190614211710.GQ1513@sasha-vm> 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 Fri, 14 Jun 2019, Sasha Levin wrote: > On Fri, Jun 14, 2019 at 01:15:23PM +0200, Thomas Gleixner wrote: > > On Thu, 30 May 2019, Michael Kelley wrote: > > > Vincenzo -- these changes for Hyper-V are a subset of a larger patch set > > > I have that moves all of the Hyper-V clock/timer code into a separate > > > clocksource driver in drivers/clocksource, with an include file in > > > includes/clocksource. That new include file should be able to work > > > instead of your new mshyperv-tsc.h. It also has the benefit of being > > > ISA neutral, so it will work with my in-progress patch set to support > > > Linux on Hyper-V on ARM64. See https://lkml.org/lkml/2019/5/27/231 > > > for the new clocksource driver patch set. > > > > Grrr. That's queued in hyperv-next for whatever reasons. > > I queue up our future pull requests there to give them some soaking in > -next. What? You queue completely unreviewed stuff which touches two other subsystems to let it soak in next? > > Sasha, can you please provide me the branch to pull from so I can have a > > common base for all the various changes floating around? > > I'll send you a unified pull request for these changes. Which has not materialized yet. TBH, I'm pretty grumpy about those clocksource changes. Here is the diffstat: MAINTAINERS | 2 arch/x86/entry/vdso/vclock_gettime.c | 1 arch/x86/entry/vdso/vma.c | 2 arch/x86/hyperv/hv_init.c | 91 --------- arch/x86/include/asm/hyperv-tlfs.h | 6 arch/x86/include/asm/mshyperv.h | 81 +------- arch/x86/kernel/cpu/mshyperv.c | 2 arch/x86/kvm/x86.c | 1 drivers/clocksource/Makefile | 1 drivers/clocksource/hyperv_timer.c | 322 +++++++++++++++++++++++++++++++++++ drivers/hv/Kconfig | 3 drivers/hv/hv.c | 156 ---------------- drivers/hv/hv_util.c | 1 drivers/hv/hyperv_vmbus.h | 3 drivers/hv/vmbus_drv.c | 42 ++-- include/clocksource/hyperv_timer.h | 105 +++++++++++ While the world and some more people have been CC'ed on those patches, neither the clocksource nor the x86 maintainer have been. When I gave Vincenzo the advise to base his code on that hyper-v branch, I expected that I find the related patches in my mail backlog. No, they have not been there because I was not on CC. Folks, please stop chosing Cc lists as you like. We have well established rules for that. And please stop queueing random unreviewed patches in next. Next is not a playground for not ready and unreviewed stuff. No, the hyper-v inbreed Reviewed-by is not sufficient for anything x86 and clocksource related. After chasing and looking at those patches, which have horrible subject lines and changelogs btw, I was not able to judge quickly whether that stuff is self contained or not. So no, I fixed up the fallout and rebased Vincenzos VDSO stuff on mainline w/o those hyperv changes simply because if they are not self contained they will break bisection badly. I'm going to push out the VDSO series later today. That will nicely break in combination with the hyper-next branch. Stephen, please drop that and do not try to handle the fallout. That stuff needs to go through the proper channels or at least be acked/reviewed by the relevant maintainers. So the hyper-v folks can rebase themself and post it proper. Yours grumpy, tglx