mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Mahlkuch <kmahlkuc@linux.ibm.com>
To: Shivaprasad G Bhat <sbhat@linux.ibm.com>,
	njavali@marvell.com, GR-QLogic-Storage-Upstream@marvell.com,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	alex.williamson@nvidia.com
Subject: Re: [PATCH] [SCSI] qla2xxx: Handle the INTx not connected while passing through
Date: Thu, 18 Jun 2026 11:56:11 -0500	[thread overview]
Message-ID: <75268c28-c937-47c4-aba1-9ff47d9cd9a2@linux.ibm.com> (raw)
In-Reply-To: <177885270578.1573.14283751510936407585.stgit@linux.ibm.com>

> The PCI_INTERRUPT_PIN reports if the device supports the INTx.
> However, when the device is assigned to a guest via vfio, the
> PCI_INTERRUPT_PIN is set to 0(i.e none) if the line is not
> connected and|or the platform cannot route the interrupt.
> 
> In such cases, the guest PCI_INTERRUPT_PIN is 0 and the port
> number becomes -1(255, uint8_t underflow) for qla[25|27|28]xx and
> qla2031 devices. The flt_region_nvram is never set, and subsequently
> the lun detection fails. Below warnings show the NVRAM configuration
> failure.
> 
>   []-0073:1: Inconsistent NVRAM checksum=0xffffffc0 id=HCAM version=0x100.
>   []-0074:1: Falling back to functioning (yet invalid -- WWPN) defaults.
>   []-0076:1: NVRAM configuration failed.
> 
> The patch handles the case, and sets the port_no to devfn like
> its done everywhere else.
> 
> Reference: commit 2bd42b03ab6b ("vfio/pci: Virtualize zero INTx PIN if no pdev->irq")
> Signed-off-by: Shivaprasad G Bhat <sbhat@linux.ibm.com>

Hi Shiva,
Your changes look reasonable and fix a known bug.

Reviewed-by: Kyle Mahlkuch <kmahlkuc@linux.ibm.com>

  parent reply	other threads:[~2026-06-18 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 13:45 Shivaprasad G Bhat
2026-06-03  8:12 ` Madhavan Srinivasan
2026-06-03 10:56   ` Shivaprasad G Bhat
2026-06-18 16:56 ` Kyle Mahlkuch [this message]
2026-07-29  2:55 ` Martin K. Petersen
2026-08-07  8:23   ` Shivaprasad G Bhat
2026-08-07 14:45     ` Martin K. Petersen

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=75268c28-c937-47c4-aba1-9ff47d9cd9a2@linux.ibm.com \
    --to=kmahlkuc@linux.ibm.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alex.williamson@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.com \
    --cc=sbhat@linux.ibm.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

all inboxes | Powered by JetHome®