Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3599938ybl; Mon, 3 Feb 2020 03:16:35 -0800 (PST) X-Google-Smtp-Source: APXvYqyGAG9gz9SJCBGvf2SMjz+TEUc6KfLTG1DyWe0dgnWDqt2ZKGMz8dEenALnc1j9XTTUr+cj X-Received: by 2002:a05:6808:350:: with SMTP id j16mr8255444oie.168.1580728594840; Mon, 03 Feb 2020 03:16:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580728594; cv=none; d=google.com; s=arc-20160816; b=g5hZNozaKl8CDehVa7JY0R0jeJ/vu8MSBSSXwsJHDpb0JSdI7HRSOcXbaJYoNM6tVE Enm6eBFDGxX7YqIqiMaHPMTeJ7ZjHAS0qpt0k++z0RunkYEUABhJuK7sDGqZMs+frI7h goj5+0g9cz0JShfO1XTTm9LG/kuQbV5oT0tIomGx4zDKHC8QDy4TfEL8CQTWL+ZkhoHN ARf+/iPX4ozS8tIGrZ1lqeRqMhU1aEZxEJ/J45idhKRl7o63bRG1Ikgl1PUAwM1/ohTF jfe8isw5zLIccTIRRrIk3H53l39LhqOB+K7KVhVWLupqKOomqsffA2LwQsk0p6ELYdbC kqrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=Ug26zZ8NwNX6MbD6XFC1XGn9DuxiiYnmekD3r0bSHbs=; b=B9e0kRjkTZez1UTvG2ol+42H7M/grY0d4GeG/uUnPXCAJx8x/nVt3L2m4RSbTTSsk4 8hV2n9WqPKRiBc5NR0N8jBVocdQSc75xic5ueVygJ0Qp/3K6TwsBgBJHgAGVLJ7Akvnr xw0CA4+ttYOX3TayaitPCChyHI/cGtIfLhwYMl0LXeMZgAf0owVGLZ7ykMeWQmtVyCIM QS1mvDxi4bqZJSCSGsVXJo5WdC3qhI1wxgkfrUi8zMYe0pZYKr1QSrXGbE5rjFBY840y AF4W76v2vwUWwWX9ZtaNSyA5rSwhfwjgXuMNGca5ATVjQaSxHlrjfvWEzMcDKicpM0Iu 2fnw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@thegoodpenguin-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=EMKBtmen; 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 r66si3222514oie.255.2020.02.03.03.16.22; Mon, 03 Feb 2020 03:16:34 -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=@thegoodpenguin-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=EMKBtmen; 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 S1727963AbgBCJlX (ORCPT + 99 others); Mon, 3 Feb 2020 04:41:23 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:50875 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727918AbgBCJlX (ORCPT ); Mon, 3 Feb 2020 04:41:23 -0500 Received: by mail-wm1-f68.google.com with SMTP id a5so14972276wmb.0 for ; Mon, 03 Feb 2020 01:41:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thegoodpenguin-co-uk.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Ug26zZ8NwNX6MbD6XFC1XGn9DuxiiYnmekD3r0bSHbs=; b=EMKBtmenrbdEvZ13+jrPUkndzYHG4j3jJkw0MuFUP8A7i4RJzU7rdZ821A0bv47wTc q9jM3YhkiYtqNfBQjeX+btm0e0Z3W+PECcTkdmm6gRMEKjQ6RzbRa1A+WSO+PN4DCwE2 G7zfQDsQ8lJB5Lleekcd3WscSL3mCHyxqJRJngPscEIaoZPrIg7r3CDGGW+kSgGxSs2j zAyIyF4p3tb02R8jDiuRxSUM3XrldR42iXwwbkDee5YWCKgPTS/8nqdAOcXqfy0zTvIC YTvo26+sR86NEW53pnCrUJYfjB8Yf7iTvvV8Iw0C7yt0jDbR0l+XOV4ipBzkLcVT8B4R UTBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Ug26zZ8NwNX6MbD6XFC1XGn9DuxiiYnmekD3r0bSHbs=; b=t8y1B1SIIik/3T+2mZLNT0+U44r3cp6TLUab084Tkhv7C3xl3AF3xIfbhe/qziN9iv xcKV7mv0mgQqjeHM9k2rb/AeKdYjUrgm/1krOw+s2WavU6XyV6/QoM7SjXxz6LXpWi7I PBu4j8lOQYFEpncBPwutd24S2gUxdfSZCEVRsSqTZWffbOWwVJy1a6Si+14rvqdcK+B6 hbM6vsXGhq2FuCoyaBr75GxgWwjHjqKgFNOx/6EjIjPk8jPsWTaoojcAEHMElFitbY+r 6+mi2SRDxMqg8G+Zdh3HJ7G0RhJw/6k0NIH9rMUniNPq9qrDEYwd1CmTaLAVq5mrt1HS jDzA== X-Gm-Message-State: APjAAAX+kQA91PJ/8WuIY5IieoUPaLqLiAuuuGULN2tgr5QFHFCkcdna tA6amxD0XuQ2iH2Xm2DzNblqQg== X-Received: by 2002:a1c:5445:: with SMTP id p5mr27657789wmi.75.1580722880976; Mon, 03 Feb 2020 01:41:20 -0800 (PST) Received: from big-machine ([2a00:23c5:dd80:8400:459c:4174:f0ee:1b26]) by smtp.gmail.com with ESMTPSA id s8sm20064267wmf.45.2020.02.03.01.41.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Feb 2020 01:41:20 -0800 (PST) Date: Mon, 3 Feb 2020 09:41:18 +0000 From: Andrew Murray To: Boqun Feng Cc: linux-pci@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Michael Kelley , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Sasha Levin , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org, Lorenzo Pieralisi , Andrew Murray , Bjorn Helgaas Subject: Re: [PATCH v2 2/3] PCI: hv: Move retarget related structures into tlfs header Message-ID: <20200203094118.GD20189@big-machine> References: <20200203050313.69247-1-boqun.feng@gmail.com> <20200203050313.69247-3-boqun.feng@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200203050313.69247-3-boqun.feng@gmail.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 03, 2020 at 01:03:12PM +0800, Boqun Feng wrote: > Currently, retarget_msi_interrupt and other structures it relys on are > defined in pci-hyperv.c. However, those structures are actually defined > in Hypervisor Top-Level Functional Specification [1] and may be > different in sizes of fields or layout from architecture to > architecture. Therefore, this patch moves those definitions into x86's Nit: Rather than 'Therefore, this patch moves ...' - how about 'Let's move ...'? > tlfs header file to support virtual PCI on non-x86 architectures in the > future. > > Besides, while I'm at it, rename retarget_msi_interrupt to Nit: 'Besides, while I'm at it' - this type of wording describes what *you've* done rather than what the patch is doing. You could replace that quoted text with 'Additionally, ' > hv_retarget_msi_interrupt for the consistent name convention, also Nit: s/name/naming > mirroring the name in TLFS. > > [1]: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/tlfs > > Signed-off-by: Boqun Feng (Microsoft) > --- > arch/x86/include/asm/hyperv-tlfs.h | 31 ++++++++++++++++++++++++++ > drivers/pci/controller/pci-hyperv.c | 34 ++--------------------------- > 2 files changed, 33 insertions(+), 32 deletions(-) > > diff --git a/arch/x86/include/asm/hyperv-tlfs.h b/arch/x86/include/asm/hyperv-tlfs.h > index 739bd89226a5..4a76e442481a 100644 > --- a/arch/x86/include/asm/hyperv-tlfs.h > +++ b/arch/x86/include/asm/hyperv-tlfs.h > @@ -911,4 +911,35 @@ struct hv_tlb_flush_ex { > struct hv_partition_assist_pg { > u32 tlb_lock_count; > }; > + > +struct hv_interrupt_entry { > + u32 source; /* 1 for MSI(-X) */ > + u32 reserved1; > + u32 address; > + u32 data; > +} __packed; Why have you added __packed here? There is no mention of this change in the commit log? Is it needed? > + > +/* > + * flags for hv_device_interrupt_target.flags > + */ > +#define HV_DEVICE_INTERRUPT_TARGET_MULTICAST 1 > +#define HV_DEVICE_INTERRUPT_TARGET_PROCESSOR_SET 2 > + > +struct hv_device_interrupt_target { > + u32 vector; > + u32 flags; > + union { > + u64 vp_mask; > + struct hv_vpset vp_set; > + }; > +} __packed; Same here. > + > +/* HvRetargetDeviceInterrupt hypercall */ > +struct hv_retarget_device_interrupt { > + u64 partition_id; Why drop the 'self' comment? > + u64 device_id; > + struct hv_interrupt_entry int_entry; > + u64 reserved2; > + struct hv_device_interrupt_target int_target; > +} __packed __aligned(8); > #endif > diff --git a/drivers/pci/controller/pci-hyperv.c b/drivers/pci/controller/pci-hyperv.c > index aacfcc90d929..0d9b74503577 100644 > --- a/drivers/pci/controller/pci-hyperv.c > +++ b/drivers/pci/controller/pci-hyperv.c > @@ -406,36 +406,6 @@ struct pci_eject_response { > > static int pci_ring_size = (4 * PAGE_SIZE); > > -struct hv_interrupt_entry { > - u32 source; /* 1 for MSI(-X) */ > - u32 reserved1; > - u32 address; > - u32 data; > -}; > - > -/* > - * flags for hv_device_interrupt_target.flags > - */ > -#define HV_DEVICE_INTERRUPT_TARGET_MULTICAST 1 > -#define HV_DEVICE_INTERRUPT_TARGET_PROCESSOR_SET 2 > - > -struct hv_device_interrupt_target { > - u32 vector; > - u32 flags; > - union { > - u64 vp_mask; > - struct hv_vpset vp_set; > - }; > -}; > - > -struct retarget_msi_interrupt { > - u64 partition_id; /* use "self" */ > - u64 device_id; > - struct hv_interrupt_entry int_entry; > - u64 reserved2; > - struct hv_device_interrupt_target int_target; > -} __packed __aligned(8); > - > /* > * Driver specific state. > */ > @@ -482,7 +452,7 @@ struct hv_pcibus_device { > struct workqueue_struct *wq; > > /* hypercall arg, must not cross page boundary */ > - struct retarget_msi_interrupt retarget_msi_interrupt_params; > + struct hv_retarget_device_interrupt retarget_msi_interrupt_params; > > /* > * Don't put anything here: retarget_msi_interrupt_params must be last > @@ -1178,7 +1148,7 @@ static void hv_irq_unmask(struct irq_data *data) > { > struct msi_desc *msi_desc = irq_data_get_msi_desc(data); > struct irq_cfg *cfg = irqd_cfg(data); > - struct retarget_msi_interrupt *params; > + struct hv_retarget_device_interrupt *params; pci-hyperv.c also makes use of retarget_msi_interrupt_lock - it's really clear from this name what it protects, however your rename now makes this more confusing. Likewise there is a comment in hv_pci_probe that refers to retarget_msi_interrupt_params which is now stale. It may be helpful to rename hv_retarget_device_interrupt for consistency with the docs - however please make sure you catch all the references - I'd suggest that the move and the rename are in different patches. Thanks, Andrew Murray > struct hv_pcibus_device *hbus; > struct cpumask *dest; > cpumask_var_t tmp; > -- > 2.24.1 >