Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sat, 5 Jun 2021 10:25:33 +0000
From:   Wei Liu <wei.liu@kernel.org>
To:     Sunil Muthuswamy <sunilmut@microsoft.com>
Cc:     Michael Kelley <mikelley@microsoft.com>,
        KY Srinivasan <kys@microsoft.com>,
        Haiyang Zhang <haiyangz@microsoft.com>,
        Stephen Hemminger <sthemmin@microsoft.com>,
        "wei.liu@kernel.org" <wei.liu@kernel.org>,
        "tglx@linutronix.de" <tglx@linutronix.de>,
        "mingo@redhat.com" <mingo@redhat.com>,
        "bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: [PATCH 1/1] Drivers: hv: Move Hyper-V extended capability check
 to arch neutral code
Message-ID: <20210605102533.uzvd4l7el2afes5i@liuwe-devbox-debian-v2>
References: <1622669804-2016-1-git-send-email-mikelley@microsoft.com>
 <MW4PR21MB20040751A1A5AFF8D6C6FCA3C03B9@MW4PR21MB2004.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <MW4PR21MB20040751A1A5AFF8D6C6FCA3C03B9@MW4PR21MB2004.namprd21.prod.outlook.com>
Precedence: bulk

On Fri, Jun 04, 2021 at 12:14:09AM +0000, Sunil Muthuswamy wrote:
> > The extended capability query code is currently under arch/x86, but it
> > is architecture neutral, and is used by arch neutral code in the Hyper-V
> > balloon driver. Hence the balloon driver fails to build on other
> > architectures.
> > 
> > Fix by moving the ext cap code out from arch/x86.  Because it is also
> > called from built-in architecture specific code, it can't be in a module,
> > so the Makefile treats as built-in even when CONFIG_HYPERV is "m".  Also
> > drivers/Makefile is tweaked because this is the first occurrence of a
> > Hyper-V file that is built-in even when CONFIG_HYPERV is "m".
> > 
> > While here, update the hypercall status check to use the new helper
> > function instead of open coding. No functional change.
> > 
> 
> Thanks for taking care of this, Michael.
> 
> Reviewed-by: Sunil Muthuswamy <sunilmut@microsoft.com>

Applied to hyperv-next. Thanks.