Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp1139962imm; Thu, 5 Jul 2018 15:47:55 -0700 (PDT) X-Google-Smtp-Source: AAOMgpciKADz0KVL7kOd2x8GOLg+QmfgXgRvnEp64SKGudmbtwTMrb4intjG/IKuQ5alQNlsnKqu X-Received: by 2002:a63:214f:: with SMTP id s15-v6mr5337630pgm.267.1530830875705; Thu, 05 Jul 2018 15:47:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530830875; cv=none; d=google.com; s=arc-20160816; b=Xo7DBupgJ86hjIf2xYqgepBbgWQNiHz9+sRw6k+ukiI8ToUJglNEiUeZpdEcuqh4kL Iy0+b+wwCv2Gb/i84Qq5axYzRJ6X1k7VDQWqhMl4L9h/yIOev/rv+OjNFIXkUs7WuKn5 Lt4FR501Qp5gT5F98Wtgg8UxIYpu2/H3gGUAQ4EsQi6//zAEDvoird1dMthmd21JXkqS o9ZOMVehu9PDEvTShC+mOm2LyPlL+yt2yktr6rQ0GPreoYoXVewUQAOGOp1E08sHsdp6 CjUG8OA8BYhI2yUiUdcqQ0V0H9O65Ied3fRHN3DFI5N/es+8eX1isd7CNDct8FFoSYBn 7cqQ== 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 :arc-authentication-results; bh=rWKFIAuGGX4D0VoP/tZ4vxR2TG1wiBSqd2eWmO6YUPQ=; b=EsvJflBs7x9II0/xgA71UjFuVSz6N2xmJsQYMwUP7g0KHHqg9Og7VfW6z2q5/qQILf /GHWgE4PvoGrRRNXIcE/UMtYZCR2rZvf5aLoxj6zSY6pO/xeW3FmfgSKf99pRWOuP81x mMFXcAiRaYVyJWBJ1Xy0wQZPtjZCy5pU6qI+/e9D6wogQHuEdnFOAApXsOudrmK33QSf DSTODCX+phGqJmlxvDTmwM85ZjwSPaBcrpMrq5xdu2J3GYUc0HICEt3cr0h4931pXMxZ dQW2sNConyDnblT/OVAr6kbGYH+zeS2jFmCi+CCXJRQV5wwb3RfpSWrFGY9sRr8DElBe Ga+g== 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 9-v6si6700467pgu.130.2018.07.05.15.47.29; Thu, 05 Jul 2018 15:47:55 -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 S1753254AbeGEWq0 (ORCPT + 99 others); Thu, 5 Jul 2018 18:46:26 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:53025 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753001AbeGEWq0 (ORCPT ); Thu, 5 Jul 2018 18:46:26 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fbD13-0005s7-Sb; Fri, 06 Jul 2018 00:46:22 +0200 Date: Fri, 6 Jul 2018 00:46:21 +0200 (CEST) From: Thomas Gleixner To: Ingo Molnar cc: KY Srinivasan , "x86@kernel.org" , "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "jasowang@redhat.com" , "hpa@zytor.com" , Stephen Hemminger , "Michael Kelley (EOSG)" , "vkuznets@redhat.com" Subject: Re: [PATCH 1/1] X86/Hyper-V:: Fix the circular dependency in IPI enlightenment. In-Reply-To: <20180705222302.GB5410@gmail.com> Message-ID: References: <20180703230155.15160-1-kys@linuxonhyperv.com> <20180704161039.GA23658@gmail.com> <20180705153820.GA26768@gmail.com> <20180705222302.GB5410@gmail.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 Fri, 6 Jul 2018, Ingo Molnar wrote: > * KY Srinivasan wrote: > > I am confused. The label ipi_mask_done was introduced in this patch > > (the patch under question fixes a circular dependency in this patch): > > > > commit 68bb7bfb7985df2bd15c2dc975cb68b7a901488a > > Author: K. Y. Srinivasan > > Date: Wed May 16 14:53:31 2018 -0700 > > > > X86/Hyper-V: Enable IPI enlightenments > > > > Hyper-V supports hypercalls to implement IPI; use them. > > > > Signed-off-by: K. Y. Srinivasan > > Signed-off-by: Thomas Gleixner > > Reviewed-by: Michael Kelley > > > > This patch was committed by Thomas some weeks ago and is in linux-next. > > This patch is also in 4.18-rc3. > > And then that name was changed to a different label in: > > 4bd06060762b: x86/hyper-v: Use cheaper HVCALL_SEND_IPI hypercall when possible > > So maybe you were testing on an older kernel. Could you try the latest -tip? The problem is that the wreckage is in Linus tree and needs to be fixed there, i.e. via x86/urgent. Now we have the new bits queued in x86/hyperv already which collide. So we need to merge x86/urgent into x86/hyperv after applying the fix and mop up the merge wreckage in x86/hyperv. I'll have a look tomorrow morning unless you beat me to it. Thanks, tglx