Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2720148pxb; Thu, 3 Feb 2022 12:42:42 -0800 (PST) X-Google-Smtp-Source: ABdhPJz6D0J85zNWDH4fcYCXE3XG603WLw3OBlek9FQek4EXjqM949somTgcJxe0SA4n8ec6JAV1 X-Received: by 2002:a50:d907:: with SMTP id t7mr37750752edj.59.1643920962270; Thu, 03 Feb 2022 12:42:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643920962; cv=none; d=google.com; s=arc-20160816; b=kYuJgsFPwYC0+T0ur2IlBEHnO+HzCZvqNpjsngTLzMpPOPVCTdQgH+Q7qRuRrbOyBY DZ/LEJikxwbAhVAj3XqTWymMtNFm3RqLGRI6er8choiDche5l5YNCwiDVd4Q2H5CGXXO vpTbIFJ6aic3qdObyTnbCQuMlrBBMi4ycJ7qyM2OzLjizWXqeuGZH6K5p64vqG9baFLK 0jagFk2p0GbdbA5RzNtS9Mb2MMrK8h4SOQZFrvWZtfEg98EnXdUBVPa5DyBnpV2w6j+2 HR3Yr3girxXcGuEX4z4OFsPuwTwk8yWLwS13a+k7jLHbODTfFm88ULzdQv7rAftZc89n 0zPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=i6eyt715/Oog9PSfSfbL4IyVRLYnAoeA6JCfl915mMY=; b=BvpSxmC4m2u1yrNpA64VHyClZzwWCIxI7rHFvAq+2/gH/hrM5VLheAwsGvjNHwF0VM iR3Pg0z/nZhB3BlyaG49RZ0uGwhEr64oR3eMUBvPJqnpmq7DMNS4iT7qeGkiqMimN2oM wW+oe7KR80CwNAVPgQJ1xN1pb5tkymHZsJyUGc3wqVuG/sSePRdamNLjasxkPPT3tHPu JZyzeQSCsH+qnsEDOeFfAB1nWCcjcci95vXEJVoKiRhhYffMnBfxL6T7tnWakHPHvyGB UCUMF2gZbx9wf1hNs07/gcXldNoLZWpU/BUYvxk3gN6A5wCj9rXI6l3fwyemZMMdhqIt riig== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g23si13339024edj.75.2022.02.03.12.42.16; Thu, 03 Feb 2022 12:42:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350573AbiBCMmx (ORCPT + 99 others); Thu, 3 Feb 2022 07:42:53 -0500 Received: from foss.arm.com ([217.140.110.172]:44652 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230213AbiBCMmx (ORCPT ); Thu, 3 Feb 2022 07:42:53 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8875711D4; Thu, 3 Feb 2022 04:42:52 -0800 (PST) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9DAF63F774; Thu, 3 Feb 2022 04:42:51 -0800 (PST) Date: Thu, 3 Feb 2022 12:42:46 +0000 From: Lorenzo Pieralisi To: longli@linuxonhyperv.com Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org, paekkaladevi@microsoft.com, Long Li Subject: Re: [Patch v4] PCI: hv: Fix NUMA node assignment when kernel boots with custom NUMA topology Message-ID: <20220203124246.GA25305@lpieralisi> References: <1643247814-15184-1-git-send-email-longli@linuxonhyperv.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1643247814-15184-1-git-send-email-longli@linuxonhyperv.com> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 26, 2022 at 05:43:34PM -0800, longli@linuxonhyperv.com wrote: > From: Long Li > > When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI > driver should only set an online NUMA node on the device. This can happen > during KDUMP where some NUMA nodes are not made online by the KDUMP kernel. > > This patch also fixes the case where kernel is booting with "numa=off". > > Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2") > Signed-off-by: Long Li > Reviewed-by: Michael Kelley > --- > Change log: > v2: use numa_map_to_online_node() to assign a node to device (suggested by > Michael Kelly ) > v3: add "Fixes" and check for num_possible_nodes() > v4: fix commit message format > > drivers/pci/controller/pci-hyperv.c | 13 +++++++++++-- > 1 file changed, 11 insertions(+), 2 deletions(-) Feel free to pick it up: Acked-by: Lorenzo Pieralisi > diff --git a/drivers/pci/controller/pci-hyperv.c b/drivers/pci/controller/pci-hyperv.c > index 20ea2ee330b8..ae0bc2fee4ca 100644 > --- a/drivers/pci/controller/pci-hyperv.c > +++ b/drivers/pci/controller/pci-hyperv.c > @@ -2155,8 +2155,17 @@ static void hv_pci_assign_numa_node(struct hv_pcibus_device *hbus) > if (!hv_dev) > continue; > > - if (hv_dev->desc.flags & HV_PCI_DEVICE_FLAG_NUMA_AFFINITY) > - set_dev_node(&dev->dev, hv_dev->desc.virtual_numa_node); > + if (hv_dev->desc.flags & HV_PCI_DEVICE_FLAG_NUMA_AFFINITY && > + hv_dev->desc.virtual_numa_node < num_possible_nodes()) > + /* > + * The kernel may boot with some NUMA nodes offline > + * (e.g. in a KDUMP kernel) or with NUMA disabled via > + * "numa=off". In those cases, adjust the host provided > + * NUMA node to a valid NUMA node used by the kernel. > + */ > + set_dev_node(&dev->dev, > + numa_map_to_online_node( > + hv_dev->desc.virtual_numa_node)); > > put_pcichild(hv_dev); > } > -- > 2.25.1 >