From: "Krzysztof Wilczyński" <kw@linux.com>
To: Arun Easi <aeasi@marvell.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Girish Basrur <GBasrur@marvell.com>,
Quinn Tran <qutran@marvell.com>
Subject: Re: [PATCH 1/1] PCI/VPD: Fix blocking of VPD data in lspci for QLogic 1077:2261
Date: Sun, 7 Mar 2021 00:57:48 +0100 [thread overview]
Message-ID: <YEQW/BFDb2Ny0NaV@rocinante> (raw)
In-Reply-To: <20210303224250.12618-2-aeasi@marvell.com>
Hi Arun,
> "lspci -vvv" for Qlogic Fibre Channel HBA 1077:2261 displays
> "Vital Product Data" as "Not readable" today and thus preventing
> customers from getting relevant HBA information. Fix it by removing
> the blacklist quirk.
>
> The VPD quirk was added by [0] to avoid a system NMI; this issue has
> been long fixed in the HBA firmware. In addition, PCI also has changes
> to check the VPD size [1], so this quirk can be reverted now regardless
> of a firmware update.
>
> Some more details can be found in the following thread:
> "VPD blacklist of Marvell QLogic 1077/2261" [2].
>
> [0] 0d5370d1d852 ("PCI: Prevent VPD access for QLogic ISP2722")
> [1] 104daa71b396 ("PCI: Determine actual VPD size on first access")
> [2] https://lore.kernel.org/linux-pci/alpine.LRH.2.21.9999.2012161641230.28924@irv1user01.caveonetworks.com/
[...]
Looks good! Assuming that this won't break QLogic ISP2722 with older
firmware, like you say, it's a nice fix.
Reviewed-by: Krzysztof Wilczyński <kw@linux.com>
Krzysztof
next prev parent reply other threads:[~2021-03-06 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 22:42 [PATCH 0/1] PCI/VPD: Fix blocking of VPD data in lspci for QLogic 1077:2261 Arun Easi
2021-03-03 22:42 ` [PATCH 1/1] " Arun Easi
2021-03-06 23:57 ` Krzysztof Wilczyński [this message]
2021-04-07 22:13 ` Bjorn Helgaas
2021-04-07 22:57 ` Arun Easi
2021-04-08 17:27 ` Bjorn Helgaas
2021-04-09 19:58 ` [EXT] " Arun Easi
2021-03-24 20:04 ` [PATCH 0/1] " Arun Easi
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=YEQW/BFDb2Ny0NaV@rocinante \
--to=kw@linux.com \
--cc=GBasrur@marvell.com \
--cc=aeasi@marvell.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qutran@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