Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp360931imu; Mon, 26 Nov 2018 11:58:27 -0800 (PST) X-Google-Smtp-Source: AFSGD/Ur3nbgTjJZUb1/O5J+GFfvjVDnplcEadoo/wCIYCiB1FpLHS2nGOUygrcqcWxyghsPlbaF X-Received: by 2002:a62:931a:: with SMTP id b26mr23921574pfe.65.1543262307417; Mon, 26 Nov 2018 11:58:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543262307; cv=none; d=google.com; s=arc-20160816; b=I5SpDxe1rAkJ0gYOmOntOs2rrguBwcHCYFXSqBJUmhLcEl4TfiGihY5WFui8chlEdB iWjHA9EExpZn3N+ekgnJo5tHFG+UK639ZnQcptDaQXknGTwFaRvyaTsahOSDrGt0hm7Z FPhgIzAG9G0IVIV//OBwBo1PxlHnILktpd8fr62peuVmWlvD1Zizk1iQqYFiufTB9Kw0 26pYP+EmbBKi8rkKuKEVvY+ZkRj8ZhaKx4YgfBAnHzR59g1kDDGmOgNhrdJ/NIsINwNA qiHHdTh8yYC/hUlf1xlALJKthbObcph+8OUPRnUP4gUP5pZa427aBXGst6UggJ2MY526 3aPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=nabvjaokHbBtNh66z4PTVou40VNcI4ebrldz+aKq4/s=; b=FWWyoRh0lXrDPdvhv2FVN4iTQSMxxJPhp/iYQW+h1MYlyeF+M4+v9WbiNOwC6lWA7f R487QI+lXV2vt8lEkg5krQ1aGk6Ga9+CymeM24tc+9eUfendiWfvKC8MT04LYWfvm3Lm tbX8CrlSmMKGNeFkuvzoBA22iECLhUfMM7T/ylpjI8AK7euWBS+wCcI++ClKJhgHZws1 MT40dpr1jY1hfnyOmPF7t17zLyGq1wnpOc5Jr1ccLxn32N67pWvwUkVWzh9Ey4NWuh98 UWJaAx/YAcSBIu31VgwVd8BP4O8YKaNSjaoMsrOO5MxzsBGzVc4S4eUOzYARo4utKP9V qymQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DR+JimNZ; 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 i63si1120708pge.515.2018.11.26.11.58.10; Mon, 26 Nov 2018 11:58:27 -0800 (PST) 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=@kernel.org header.s=default header.b=DR+JimNZ; 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 S1726745AbeK0Gwm (ORCPT + 99 others); Tue, 27 Nov 2018 01:52:42 -0500 Received: from mail.kernel.org ([198.145.29.99]:59392 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726300AbeK0Gwm (ORCPT ); Tue, 27 Nov 2018 01:52:42 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id EE7CC20664; Mon, 26 Nov 2018 19:57:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543262249; bh=lNGhGzTWpw0qgtqdEHZvw7uKPMnqA1k/BXCI2eFNUcc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=DR+JimNZvWzwJUHs6wW+jt3v0iVK3pkwUcEVh1Q/EE8Ne2RBnlE9hbEcEkzUKCr+k AbTecd6vfHjnjB0IOppK1CNpmIlROLUCuWyt71sBpQikWUgfTxN1lc0ajElT/TSZeX CinHAzh2ANvOjUBI6VHPJQiGVb7UsctFKhLlgVM4= Date: Mon, 26 Nov 2018 20:57:27 +0100 From: Greg KH To: Michael Kelley Cc: KY Srinivasan , "will.deacon@arm.com" , "catalin.marinas@armm.com" , "mark.rutland@arm.com" , "marc.zyngier@arm.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "jasowang@redhat.com" , Stephen Hemminger , vkuznets Subject: Re: [PATCH 3/4] Drivers: hv: vmbus: Add hooks for per-CPU IRQ Message-ID: <20181126195727.GA9957@kroah.com> References: <20181122030914.16274-1-kys@linuxonhyperv.com> <20181122031059.16338-1-kys@linuxonhyperv.com> <20181122031059.16338-3-kys@linuxonhyperv.com> <20181126192101.GC32208@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 26, 2018 at 07:47:41PM +0000, Michael Kelley wrote: > From: Greg KH Monday, November 26, 2018 11:21 AM > > > > diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h > > > index 0d6271cce198..8d97bd3a13a6 100644 > > > --- a/arch/x86/include/asm/mshyperv.h > > > +++ b/arch/x86/include/asm/mshyperv.h > > > @@ -109,6 +109,10 @@ void hyperv_vector_handler(struct pt_regs *regs); > > > void hv_setup_vmbus_irq(void (*handler)(void)); > > > void hv_remove_vmbus_irq(void); > > > > > > +/* On x86/x64, there isn't a real IRQ to be enabled/disable */ > > > +static inline void hv_enable_vmbus_irq(void) {} > > > +static inline void hv_disable_vmbus_irq(void) {} > > > + > > > void hv_setup_kexec_handler(void (*handler)(void)); > > > void hv_remove_kexec_handler(void); > > > void hv_setup_crash_handler(void (*handler)(struct pt_regs *regs)); > > > diff --git a/drivers/hv/hv.c b/drivers/hv/hv.c > > > index 166c2501de17..d0bb09a4bd73 100644 > > > --- a/drivers/hv/hv.c > > > +++ b/drivers/hv/hv.c > > > @@ -307,6 +307,7 @@ int hv_synic_init(unsigned int cpu) > > > hv_set_siefp(siefp.as_uint64); > > > > > > /* Setup the shared SINT. */ > > > + hv_enable_vmbus_irq(); > > > hv_get_synint_state(VMBUS_MESSAGE_SINT, shared_sint.as_uint64); > > > > > > shared_sint.vector = HYPERVISOR_CALLBACK_VECTOR; > > > @@ -434,6 +435,7 @@ int hv_synic_cleanup(unsigned int cpu) > > > /* Disable the global synic bit */ > > > sctrl.enable = 0; > > > hv_set_synic_state(sctrl.as_uint64); > > > + hv_disable_vmbus_irq(); > > > > > > return 0; > > > } > > > -- > > > 2.19.1 > > > > You created "null" hooks that do nothing, for no one in this patch > > series, why? > > > > hv_enable_vmbus_irq() and hv_disable_vmbus_irq() have non-null > implementations in the ARM64 code in patch 2 of this series. The > implementations are in the new file arch/arm64/hyperv/mshyperv.c. > Or am I misunderstanding your point? So you use a hook in an earlier patch and then add it in a later one? Shouldn't you do it the other way around? As it is, the earlier patch should not work properly, right? thanks, greg k-h