[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <524C748D.8080803@linux.vnet.ibm.com>
Date: Wed, 02 Oct 2013 14:31:25 -0500
From: Brian King <brking@...ux.vnet.ibm.com>
To: Alexander Gordeev <agordeev@...hat.com>
CC: linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
"VMware, Inc." <pv-drivers@...are.com>,
linux-nvme@...ts.infradead.org, linux-ide@...r.kernel.org,
stable@...r.kernel.org, linux-s390@...r.kernel.org,
Andy King <acking@...are.com>, linux-scsi@...r.kernel.org,
linux-rdma@...r.kernel.org, x86@...nel.org,
linux-pci@...r.kernel.org, iss_storagedev@...com,
linux-driver@...gic.com, Tejun Heo <tj@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Dan Williams <dan.j.williams@...el.com>,
Jon Mason <jon.mason@...el.com>,
Ingo Molnar <mingo@...hat.com>,
Solarflare linux maintainers <linux-net-drivers@...arflare.com>,
netdev@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>,
e1000-devel@...ts.sourceforge.net,
Martin Schwidefsky <schwidefsky@...ibm.com>,
linux390@...ibm.com, linuxppc-dev@...ts.ozlabs.org,
Wendy Xiong <wenxiong@...ux.vnet.ibm.com>
Subject: Re: [PATCH RFC 36/77] ipr: Enable MSI-X when IPR_USE_MSIX type is
set, not IPR_USE_MSI
On 10/02/2013 05:48 AM, Alexander Gordeev wrote:
> Signed-off-by: Alexander Gordeev <agordeev@...hat.com>
> ---
> drivers/scsi/ipr.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
> index fb57e21..762a93e 100644
> --- a/drivers/scsi/ipr.c
> +++ b/drivers/scsi/ipr.c
> @@ -9527,7 +9527,7 @@ static int ipr_probe_ioa(struct pci_dev *pdev,
> ipr_number_of_msix = IPR_MAX_MSIX_VECTORS;
> }
>
> - if (ioa_cfg->ipr_chip->intr_type == IPR_USE_MSI &&
> + if (ioa_cfg->ipr_chip->intr_type == IPR_USE_MSIX &&
> ipr_enable_msix(ioa_cfg) == 0)
> ioa_cfg->intr_flag = IPR_USE_MSIX;
> else if (ioa_cfg->ipr_chip->intr_type == IPR_USE_MSI &&
>
Nack. ioa_cfg->ipr_chip->intr_type gets initialized from the ipr_chip table
at the top of the driver which never sets intr_type to IPR_USE_MSIX, so this
will break MSI-X support for ipr.
We indicate at the chip level only whether we want to force LSI or whether
we want to enable MSI / MSI-X and then try enabling MSI-X and fall back to
MSI if MSI-X is not available or does not work. We then set intr_flag to indicate
what we are actually using on the specific adapter.
Thanks,
Brian
--
Brian King
Power Linux I/O
IBM Linux Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists