mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Scott Branden <scott.branden@broadcom.com>
To: Breno Leitao <leitao@leitao.org>, bcm-kernel-feedback-list@broadcom.com
Cc: leit@fb.com, linux-kernel@vger.kernel.org,
	Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] misc: bcm-vk: Specify the minimum number of IRQ vecs
Date: Wed, 20 Jul 2022 09:12:44 -0700	[thread overview]
Message-ID: <e416c587-d3cc-947a-7336-2c1954e2e432@broadcom.com> (raw)
In-Reply-To: <20220719122313.500924-1-leitao@leitao.org>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

Hi Breno,

On 2022-07-19 05:23, Breno Leitao wrote:
> From: Breno Leitao <leitao@debian.org>
> 
> During bcm_vk_probe(), pci_alloc_irq_vectors() is called passing the
> number of IRQ vectors as 1, but, later, check how many IRQ vectors it
> got, and fails if it is smaller than VK_MSIX_IRQ_MIN_REQ.
> 
> The most appropriated way to do it is setting the 'min_vecs' param as
> VK_MSIX_IRQ_MIN_REQ, instead of one. pci_alloc_irq_vectors() should
> know the requirements when called.
Yes, the end result is no operational change before or after this commit.
> 
> The test was done by just loading this module on a machine with a
> Valkyrie offload engine
> 
> Signed-off-by: Breno Leitao <leitao@debian.org>
Acked-by: Scott Branden <scott.branden@broadcom.com>
> ---
>   drivers/misc/bcm-vk/bcm_vk_dev.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/misc/bcm-vk/bcm_vk_dev.c b/drivers/misc/bcm-vk/bcm_vk_dev.c
> index a16b99bdaa13..bedab17884b8 100644
> --- a/drivers/misc/bcm-vk/bcm_vk_dev.c
> +++ b/drivers/misc/bcm-vk/bcm_vk_dev.c
> @@ -1339,7 +1339,7 @@ static int bcm_vk_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>   	pci_set_drvdata(pdev, vk);
>   
>   	irq = pci_alloc_irq_vectors(pdev,
> -				    1,
> +				    VK_MSIX_IRQ_MIN_REQ,
>   				    VK_MSIX_IRQ_MAX,
>   				    PCI_IRQ_MSI | PCI_IRQ_MSIX);
>   

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]

       reply	other threads:[~2022-07-20 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220719122313.500924-1-leitao@leitao.org>
2022-07-20 16:12 ` Scott Branden [this message]
2022-08-12  9:40   ` [RESEND PATCH] " Breno Leitao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e416c587-d3cc-947a-7336-2c1954e2e432@broadcom.com \
    --to=scott.branden@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=leit@fb.com \
    --cc=leitao@debian.org \
    --cc=leitao@leitao.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®