Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2401819pxb; Thu, 3 Feb 2022 06:01:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJybo/X7V8i2HC+04Njmw+35PUGdPN564FyaHU+tF/ap2tREzHwCmMHPcGTMTyiYmtWaD89H X-Received: by 2002:a17:902:6903:: with SMTP id j3mr35992070plk.137.1643896885423; Thu, 03 Feb 2022 06:01:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643896885; cv=none; d=google.com; s=arc-20160816; b=DMfRmMI9iTjsR87oIHNYDd2AYZlbjtjMBNQoZsf4czjpEjUtU4I62we3YhmTWYPv90 Q7R9iOtQdDBAIvEu73OS71VDpjjO1kdGUBycdx6TljcOFdJNc4qD1fGcLj64DNE66AVX 3T7A+BCjb/ffU3qU0l0+ANIrFkosWr/3/E+6+9EYsrs22qv5lhOM+zKgp5Z4e6hL+wo6 Q2FvenQGhTQ99v2a35pS3VY96Mtw7X7BwGee3SD5pn6G7EQt912tmG/krUS3/e5hbysy vlPd0iI5KPBUf8KqYbM1atfmOEgW3WxGlzCfLZjz6E/qPQV7yyaQg4HQrlQ87O8f0KYI icvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=8u9eHIF4FM+XVVNXPbgpQAD1FxfIZHgwuCKElrkP4VM=; b=rzq63F06on134g7Vvv/XIFz1dnMk3fs6UlbsBvSf+3luOjRVU6EdldPE93Ssavleg3 cdiIHT6dJKf4o9KwMqsiBoAOWIzOgiSlu4h0E59EdX+QcVIrqLR41lodCZ0fDjmVDYiU KP5FQU5s0maJC7WsSdlDFjWBrVI9dhBLQHBMMv+EXp77unJSoWq3D50MdkbQFkCO61sk g3WzQg0f+jjYeNDHx7rCX5SUWb/fiffKEfmXYvzooZq9W0j3Y8zIa/JOr0l7lhdGPL48 0WyAUKNvWRHUazyhvfIIUeuU0ejiFKCCEtD8IM5SeJGq+45klKGnJdn2ybSuL5yvCW0v NOlA== 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x15si22143332pla.221.2022.02.03.06.01.11; Thu, 03 Feb 2022 06:01:25 -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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350610AbiBCMqc (ORCPT + 99 others); Thu, 3 Feb 2022 07:46:32 -0500 Received: from mail-wr1-f42.google.com ([209.85.221.42]:43722 "EHLO mail-wr1-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233627AbiBCMq3 (ORCPT ); Thu, 3 Feb 2022 07:46:29 -0500 Received: by mail-wr1-f42.google.com with SMTP id v13so4792363wrv.10; Thu, 03 Feb 2022 04:46:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=8u9eHIF4FM+XVVNXPbgpQAD1FxfIZHgwuCKElrkP4VM=; b=mE5xaII+om5/G9NqnkVstDlun0nlZLaVYMNKYozN1WqYK7KQWBH4Rm87dnCaFO64/G tI0MTBgFoFFFkjmgg/ExwliPwAYBN7TfkhcHGQ8TmBi17LFIu6m5pBOC1D53HU8gWAUJ c/ckWUnq3VbDcLnaNuPxqmqABBlsE/3MyP6jszLI4eVGEcIiI2qdy5HPDbJ3jELR2NN8 Eb5qAF/JyUKHHimYy5Q5Rv89sujKXleRFeV51GBJKZ5oR6rCBj7zDkYaMXqI98NEsdC1 5mTUVatG0E9KsEFg2BtSp6rYaMcROWFYuzR69dz+Km8QmO98zvKQdChs9j2Ay7MDhrFj WP8w== X-Gm-Message-State: AOAM530NQUC2X44u3fBh7i/IiIh3h2cHR7i0emmeGVKPMkm3RA9IFiM/ YMDuYt4VBya9tWHVnx+4jn0= X-Received: by 2002:a5d:590c:: with SMTP id v12mr27167443wrd.714.1643892388692; Thu, 03 Feb 2022 04:46:28 -0800 (PST) Received: from liuwe-devbox-debian-v2 ([51.145.34.42]) by smtp.gmail.com with ESMTPSA id l10sm1934225wry.79.2022.02.03.04.46.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Feb 2022 04:46:28 -0800 (PST) Date: Thu, 3 Feb 2022 12:46:27 +0000 From: Wei Liu To: Lorenzo Pieralisi Cc: longli@linuxonhyperv.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org, paekkaladevi@microsoft.com, Long Li , Wei Liu Subject: Re: [Patch v4] PCI: hv: Fix NUMA node assignment when kernel boots with custom NUMA topology Message-ID: <20220203124627.qudi3mmmyv4aee5w@liuwe-devbox-debian-v2> References: <1643247814-15184-1-git-send-email-longli@linuxonhyperv.com> <20220203124246.GA25305@lpieralisi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220203124246.GA25305@lpieralisi> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 03, 2022 at 12:42:46PM +0000, Lorenzo Pieralisi wrote: > 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 Thanks Lorenzo.