LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	njavali@marvell.com, James.Bottomley@HansenPartnership.com
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>,
	linux-kernel@vger.kernel.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [SCSI] qla2xxx: Handle the INTx not connected while passing through
Date: Fri, 7 Aug 2026 13:53:01 +0530	[thread overview]
Message-ID: <04e92492-8129-4b47-b103-d8954da8ce74@linux.ibm.com> (raw)
In-Reply-To: <178508193511.4027291.4543280548195278135.b4-ty@oracle.com>

Hi Martin,


On 7/29/26 8:25 AM, Martin K. Petersen wrote:
> On Fri, 15 May 2026 13:45:18 +0000, Shivaprasad G Bhat wrote:
> 
>> 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.
>>
>> [...]
> 
> Applied to 7.3/scsi-queue, thanks!

Thanks for pulling the patch. Would it possible to get this fix into 7.2 
stream as well?

Regards,
Shivaprasad
</snip>


  parent reply	other threads:[~2026-08-07  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <177885270578.1573.14283751510936407585.stgit@linux.ibm.com>
2026-06-03  8:12 ` [PATCH] [SCSI] qla2xxx: Handle the INTx not connected while passing through Madhavan Srinivasan
2026-06-03 10:56   ` Shivaprasad G Bhat
     [not found] ` <178508193511.4027291.4543280548195278135.b4-ty@oracle.com>
2026-08-07  8:23   ` Shivaprasad G Bhat [this message]
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=04e92492-8129-4b47-b103-d8954da8ce74@linux.ibm.com \
    --to=sbhat@linux.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=harshpb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.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