From: Hannes Reinecke <hare@kernel.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org,
Karan Tilak Kumar <kartilak@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>,
Satish Kharat <satishkh@cisco.com>,
Hannes Reinecke <hare@kernel.org>
Subject: [PATCH 1/4] fnic: use resulting interrupt mode during configuration
Date: Tue, 4 Nov 2025 11:04:21 +0100 [thread overview]
Message-ID: <20251104100424.8215-2-hare@kernel.org> (raw)
In-Reply-To: <20251104100424.8215-1-hare@kernel.org>
The configured interrupt mode might be different than the resulting
interrupts mode after all configuration limitations have been applied.
Signed-off-by: Hannes Reinecke <hare@kernel.org>
---
drivers/scsi/fnic/fnic_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/fnic/fnic_main.c b/drivers/scsi/fnic/fnic_main.c
index 4cc4077ea53c..7075a23d9229 100644
--- a/drivers/scsi/fnic/fnic_main.c
+++ b/drivers/scsi/fnic/fnic_main.c
@@ -678,7 +678,7 @@ void fnic_mq_map_queues_cpus(struct Scsi_Host *host)
{
struct fnic *fnic = *((struct fnic **) shost_priv(host));
struct pci_dev *l_pdev = fnic->pdev;
- int intr_mode = fnic->config.intr_mode;
+ int intr_mode = vnic_dev_get_intr_mode(fnic->vdev);
struct blk_mq_queue_map *qmap = &host->tag_set.map[HCTX_TYPE_DEFAULT];
if (intr_mode == VNIC_DEV_INTR_MODE_MSI || intr_mode == VNIC_DEV_INTR_MODE_INTX) {
--
2.43.0
next prev parent reply other threads:[~2025-11-04 10:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 10:04 [PATCH 0/4] fnic: fixup INTx and MSI interrupt modes Hannes Reinecke
2025-11-04 10:04 ` Hannes Reinecke [this message]
2025-11-04 23:17 ` [PATCH 1/4] fnic: use resulting interrupt mode during configuration Karan Tilak Kumar (kartilak)
2025-11-06 21:56 ` Karan Tilak Kumar (kartilak)
2025-11-04 10:04 ` [PATCH 2/4] fnic: correctly initialize 'fnic->name' Hannes Reinecke
2025-11-04 23:18 ` Karan Tilak Kumar (kartilak)
2025-11-06 21:57 ` Karan Tilak Kumar (kartilak)
2025-11-04 10:04 ` [PATCH 3/4] fnic: missing initialisation for wq_copy_base Hannes Reinecke
2025-11-04 23:19 ` Karan Tilak Kumar (kartilak)
2025-11-06 22:00 ` Karan Tilak Kumar (kartilak)
2025-11-04 10:04 ` [PATCH 4/4] fnic: make interrupt mode configurable Hannes Reinecke
2025-11-04 23:21 ` Karan Tilak Kumar (kartilak)
2025-11-06 22:09 ` Karan Tilak Kumar (kartilak)
2025-11-07 8:29 ` Hannes Reinecke
2025-11-07 22:23 ` Karan Tilak Kumar (kartilak)
2026-01-14 17:02 ` Karan Tilak Kumar (kartilak)
2026-01-23 18:21 ` Lee Duncan
2026-01-23 18:37 ` Karan Tilak Kumar (kartilak)
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=20251104100424.8215-2-hare@kernel.org \
--to=hare@kernel.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=kartilak@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.com \
/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