Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3807040imj; Tue, 12 Feb 2019 05:07:10 -0800 (PST) X-Google-Smtp-Source: AHgI3IZfCQj+B9jVAMWcLh24J5ocHBWc93EFZSFPkHuUnSi/3JfPZ45NFQRta1/c5fN6Xfgtc0nJ X-Received: by 2002:a63:854a:: with SMTP id u71mr3499368pgd.141.1549976830657; Tue, 12 Feb 2019 05:07:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549976830; cv=none; d=google.com; s=arc-20160816; b=JzFwBpwWC7/4M6GJOHS+EvWfCoSKSOcUK8WkXPT5JulT7RULaQM8MQHe1mBYsSBvij 9Cf7ERt2tIxFOg6djN74foVsNApOjHybfSOigjKTwuza9L4JiigcIANBHFuOP8L8aMPp mPmuGdvM62pMIIlDA7Sm0tDTvznRf21jnDVPAkf+XInXilWlXzBF4+Jsl5Va/q4tlf5K 8CCyug4GkqQIRv2LETd8+MJQ3G9QBsUXNL0AQgUjfqWsqORBXBuiw8KI52SwcRr931an o/BBbd2L3/tbedRcmsvzGaSoMOM3lYwcvJ5GVPvQ5ERIDayAIE/UqeDFrwnuY6o5XGPi fgoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=ujCZq6SjT/ntJGQd70l3NrbnfgCYs5W9f3dXihZ+iRo=; b=EpNDK4pyaagnHIEY+OLY6csleTvynR7ii61pXWe48ZTTBabaNX5bZ2q3nV77N5mcSJ OgXq2kOaZFI9HDZuimvjBOvCj+Ak8nIrxx6ilHs75DXfDli3MPdJalRQMq1/29iWaEtV kaBJKEV3dnwM4175mqNd3O1ZteqGPTb3RibLh0UdJPmtNfIWZpTtf5NSJg7b2aNg8Xel 36WiTdv8ySh0DyFd3Q+FzJI10BI4wipiRQ2olousDs7GlROgHKTMgRc3CWYjGYSa3JKH OLIGgWss+ZnwlhUbuKnhMckQ4mXUEJtNKUp3Kt+vQ7pmLaE5k8SVBwx7wGoCTCYJyqhQ ibeQ== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n5si13170034pgc.563.2019.02.12.05.06.52; Tue, 12 Feb 2019 05:07:10 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729622AbfBLNFW (ORCPT + 99 others); Tue, 12 Feb 2019 08:05:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53544 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727750AbfBLNFW (ORCPT ); Tue, 12 Feb 2019 08:05:22 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BCF7BA7875; Tue, 12 Feb 2019 13:05:21 +0000 (UTC) Received: from localhost (ovpn-8-25.pek2.redhat.com [10.72.8.25]) by smtp.corp.redhat.com (Postfix) with ESMTP id 55991101E845; Tue, 12 Feb 2019 13:05:17 +0000 (UTC) From: Ming Lei To: Christoph Hellwig , Bjorn Helgaas , Thomas Gleixner Cc: Jens Axboe , linux-block@vger.kernel.org, Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Keith Busch , Ming Lei Subject: [PATCH V2 4/4] genirq/affinity: Document .calc_sets as required in case of multiple sets Date: Tue, 12 Feb 2019 21:04:39 +0800 Message-Id: <20190212130439.14501-5-ming.lei@redhat.com> In-Reply-To: <20190212130439.14501-1-ming.lei@redhat.com> References: <20190212130439.14501-1-ming.lei@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 12 Feb 2019 13:05:21 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Now NVMe has implemented the .calc_sets callback for caculating each set's vectors. For other cases of multiple irq sets, it isn't a good way to pre-caculate each set's vectors before allocating IRQ vectors because NVMe's same issue exists too. Document .calc_sets as required explicitly for multiple sets. Signed-off-by: Ming Lei --- drivers/pci/msi.c | 4 ++-- include/linux/interrupt.h | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c index 4c0b47867258..9f91fa713141 100644 --- a/drivers/pci/msi.c +++ b/drivers/pci/msi.c @@ -1039,7 +1039,7 @@ static int __pci_enable_msi_range(struct pci_dev *dev, int minvec, int maxvec, * If the caller is passing in sets, we can't support a range of * vectors. The caller needs to handle that. */ - if (affd && affd->nr_sets && minvec != maxvec) + if (affd && affd->nr_sets > 1 && !affd->calc_sets) return -EINVAL; if (WARN_ON_ONCE(dev->msi_enabled)) @@ -1097,7 +1097,7 @@ static int __pci_enable_msix_range(struct pci_dev *dev, * If the caller is passing in sets, we can't support a range of * supported vectors. The caller needs to handle that. */ - if (affd && affd->nr_sets && minvec != maxvec) + if (affd && affd->nr_sets > 1 && !affd->calc_sets) return -EINVAL; if (WARN_ON_ONCE(dev->msix_enabled)) diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h index 7a27f6ba1f2f..a053f7fb0ff1 100644 --- a/include/linux/interrupt.h +++ b/include/linux/interrupt.h @@ -269,7 +269,8 @@ struct irq_affinity_notify { * the MSI(-X) vector space * @nr_sets: Length of passed in *sets array * @set_vectors: Number of affinitized sets - * @calc_sets: Callback for caculating set vectors + * @calc_sets: Callback for caculating set vectors, required for + * multiple irq sets. * @priv: Private data of @calc_sets */ struct irq_affinity { -- 2.9.5