From: Allen Hubbe <Allen.Hubbe@emc.com>
To: linux-ntb@googlegroups.com
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>
Subject: [PATCH v2 04/17] NTB: Check the device ID to set errata flags
Date: Thu, 21 May 2015 04:20:48 -0400 [thread overview]
Message-ID: <ad7b20129288ff27c1c8d57a16da373fde9451fb.1432196075.git.Allen.Hubbe@emc.com> (raw)
In-Reply-To: <cover.1432192681.git.Allen.Hubbe@emc.com>
In-Reply-To: <cover.1432196075.git.Allen.Hubbe@emc.com>
From: Dave Jiang <dave.jiang@intel.com>
Set errata flags for the specific device IDs to which they apply,
instead of the whole xeon hardware class.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
---
drivers/ntb/hw/intel/ntb_hw_intel.c | 49 +++++++++++++++++++++++++++++++++----
1 file changed, 44 insertions(+), 5 deletions(-)
diff --git a/drivers/ntb/hw/intel/ntb_hw_intel.c b/drivers/ntb/hw/intel/ntb_hw_intel.c
index 2acb19b..89fea50 100644
--- a/drivers/ntb/hw/intel/ntb_hw_intel.c
+++ b/drivers/ntb/hw/intel/ntb_hw_intel.c
@@ -1722,29 +1722,68 @@ static int snb_init_dev(struct intel_ntb_dev *ndev)
u8 ppd;
int rc, mem;
+ pdev = ndev_pdev(ndev);
+
+ switch (pdev->device) {
/* There is a Xeon hardware errata related to writes to SDOORBELL or
* B2BDOORBELL in conjunction with inbound access to NTB MMIO Space,
* which may hang the system. To workaround this use the second memory
* window to access the interrupt and scratch pad registers on the
* remote system.
*/
- ndev->hwerr_flags |= NTB_HWERR_SDOORBELL_LOCKUP;
+ case PCI_DEVICE_ID_INTEL_NTB_SS_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_HSX:
+ ndev->hwerr_flags |= NTB_HWERR_SDOORBELL_LOCKUP;
+ break;
+ }
+ switch (pdev->device) {
/* There is a hardware errata related to accessing any register in
* SB01BASE in the presence of bidirectional traffic crossing the NTB.
*/
- ndev->hwerr_flags |= NTB_HWERR_SB01BASE_LOCKUP;
+ case PCI_DEVICE_ID_INTEL_NTB_SS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_HSX:
+ ndev->hwerr_flags |= NTB_HWERR_SB01BASE_LOCKUP;
+ break;
+ }
+ switch (pdev->device) {
/* HW Errata on bit 14 of b2bdoorbell register. Writes will not be
* mirrored to the remote system. Shrink the number of bits by one,
* since bit 14 is the last bit.
*/
- ndev->hwerr_flags |= NTB_HWERR_B2BDOORBELL_BIT14;
+ case PCI_DEVICE_ID_INTEL_NTB_SS_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_JSF:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_SNB:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_IVT:
+ case PCI_DEVICE_ID_INTEL_NTB_SS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_PS_HSX:
+ case PCI_DEVICE_ID_INTEL_NTB_B2B_HSX:
+ ndev->hwerr_flags |= NTB_HWERR_B2BDOORBELL_BIT14;
+ break;
+ }
ndev->reg = &snb_reg;
- pdev = ndev_pdev(ndev);
-
rc = pci_read_config_byte(pdev, SNB_PPD_OFFSET, &ppd);
if (rc)
return -EIO;
--
2.4.0.rc0.43.gcf8a8c6
next prev parent reply other threads:[~2015-05-21 13:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 8:20 [PATCH v2 00/17] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-05-21 9:45 ` Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 01/17] NTB: Move files in preparation for NTB abstraction Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 02/17] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 03/17] NTB: Enable link for Intel root port mode in probe Allen Hubbe
2015-05-21 8:20 ` Allen Hubbe [this message]
2015-05-21 8:20 ` [PATCH v2 05/17] NTB: Add parameters for Intel SNB B2B addresses Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 06/17] NTB: Add ping pong test client Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 07/17] NTB: Add tool " Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 08/17] NTB: Rate limit ntb_qp_link_work Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 09/17] NTB: Differentiate transport link down messages Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 10/17] NTB: Do not advance transport RX on link down Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 11/17] NTB: Reset transport QP link stats on down Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 12/17] NTB: Use NUMA memory and DMA chan in transport Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 13/17] NTB: Use NUMA memory in Intel driver Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 14/17] NTB: Improve performance with write combining Allen Hubbe
2015-05-21 8:20 ` [PATCH v2 15/17] NTB: Default to CPU memcpy for performance Allen Hubbe
2015-05-21 8:21 ` [PATCH v2 16/17] NTB: Fix small code format issues in transport Allen Hubbe
2015-05-21 8:21 ` [PATCH v2 17/17] NTB: Rename intel hw to proper platform names Allen Hubbe
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=ad7b20129288ff27c1c8d57a16da373fde9451fb.1432196075.git.Allen.Hubbe@emc.com \
--to=allen.hubbe@emc.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
/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®