From: "Nath, Arindam" <Arindam.Nath@amd.com>
To: "Mehta, Sanju" <Sanju.Mehta@amd.com>, Jiasen Lin <linjiasen@hygon.cn>
Cc: "S-k,
Shyam-sundar <Shyam-sundar.S-k@amd.com> Dave Jiang"
<dave.jiang@intel.com>, Allen Hubbe <allenbh@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ntb <linux-ntb@googlegroups.com>,
"linjiasen007@gmail.com" <linjiasen007@gmail.com>
Subject: RE: Fwd: [PATCH] NTB: Fix an error in get link status
Date: Tue, 26 Nov 2019 14:35:23 +0000 [thread overview]
Message-ID: <MN2PR12MB323225CC169836056288CAA39C450@MN2PR12MB3232.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c5adca66-024f-8d37-3187-ffba73102ac4@amd.com>
> -----Original Message-----
> From: Mehta, Sanju <Sanju.Mehta@amd.com>
> Sent: Tuesday, November 26, 2019 18:40
> To: Jiasen Lin <linjiasen@hygon.cn>
> Cc: S-k, Shyam-sundar <Shyam-sundar.S-k@amd.com> Dave Jiang
> <dave.jiang@intel.com>; Nath, Arindam <Arindam.Nath@amd.com>; Allen
> Hubbe <allenbh@gmail.com>; linux-kernel <linux-kernel@vger.kernel.org>;
> linux-ntb <linux-ntb@googlegroups.com>; linjiasen007@gmail.com
> Subject: Re: Fwd: [PATCH] NTB: Fix an error in get link status
>
>
> > Hi Sanjay R Mehta
> >
> > In more complex topology, read the Link Status and Control register of
> > RP is also wrong. Suppose that a PCIe switch bridge to the Secondary RP,
> > and Secondary internal SW.ds is a child device for switch's downstream
> > port as illustrated in the following topology.
> >
> > In secondary PCI domain:
> > Secondary RP--Switch UP--Switch DP--Secondary internal SW.us--
> Secondary
> > internal SW.ds--Secondary NTB
> >
> > pci_rp = pci_find_pcie_root_port(ndev->ntb.pdev) will return the
> > Secondary RP, and pcie_capability_read_dword(pci_rp,
> > PCI_EXP_LNKCTL,&stat) will get the link status between Secondary RP and
> > Switch UP. Maybe, read the Link Status and control register of Secondary
> > internal SW.us is appropriate.
> >
> Hi Jiansen Lin,
>
> I modified the code as per your suggestion and is working fine.
> Adding Arindam for comments who was the co-author of the patch I was
> about to send for upstream review.
Hi Jiansen Lin,
I am okay with the changes proposed by you. But one thing we need to keep
in mind is that, the configuration SWUS+SWDS+EP as visible from the NTB
secondary, might change in future AMD implementations where these internal
switches are not present anymore. So we might have to re-visit the patch
again later.
Thanks,
Arindam
>
> Thanks,
> Sanjay Mehta
> > struct pci_dev *pci_up = NULL;
> > struct pci_dev *pci_dp = NULL;
> >
> > if (ndev->ntb.topo == NTB_TOPO_SEC) {
> > /* Locate the pointer to Secondary up for this device */
> > pci_dp = pci_upstream_bridge(ndev->ntb.pdev);
> > /* Read the PCIe Link Control and Status register */
> > if (pci_dp) {
> > pci_up = pci_upstream_bridge(pci_dp);
> > if (pci_up) {
> > rc = pcie_capability_read_dword(pci_up, PCI_EXP_LNKCTL,
> > &stat);
> > if (rc)
> > return 0;
> > }
> > }
> > }
> >
> > Thanks,
> > Jiansen Lin
> >
> >> I have modified the code according to your suggestion and tested it
> >> on Dhyana platform, it works well, expect to receice your patch.
> >>
> >> Before modify the code, read the Link Status and control register of the
> >> secondary NTB device to get link status.
> >>
> >> cat /sys/kernel/debug/ntb_hw_amd/0000\:43\:00.1/info
> >> NTB Device Information:
> >> Connection Topology - NTB_TOPO_SEC
> >> LNK STA - 0x11030042
> >> Link Status - Up
> >> Link Speed - PCI-E Gen 3
> >> Link Width - x16
> >>
> >> After modify the code, read the Link Status and control register of the
> >> secondary RP to get link status.
> >>
> >> cat /sys/kernel/debug/ntb_hw_amd/0000\:43\:00.1/info
> >> NTB Device Information:
> >> Connection Topology - NTB_TOPO_SEC
> >> LNK STA - 0x70830042
> >> Link Status - Up
> >> Link Speed - PCI-E Gen 3
> >> Link Width - x8
> >>
> >> Thanks,
> >> Jiasen Lin
> >>
> >>> ---
> >>> drivers/ntb/hw/amd/ntb_hw_amd.c | 27
> +++++++++++++++++++++++----
> >>> drivers/ntb/hw/amd/ntb_hw_amd.h | 1 -
> >>> 2 files changed, 23 insertions(+), 5 deletions(-)
> >>>
> >>> diff --git a/drivers/ntb/hw/amd/ntb_hw_amd.c
> >>> b/drivers/ntb/hw/amd/ntb_hw_amd.c
> >>> index 14ad69c..91e1966 100644
> >>> --- a/drivers/ntb/hw/amd/ntb_hw_amd.c
> >>> +++ b/drivers/ntb/hw/amd/ntb_hw_amd.c
> >>> @@ -842,6 +842,8 @@ static inline void ndev_init_struct(struct
> >>> amd_ntb_dev *ndev,
> >>> static int amd_poll_link(struct amd_ntb_dev *ndev)
> >>> {
> >>> void __iomem *mmio = ndev->peer_mmio;
> >>> + struct pci_dev *pci_rp = NULL;
> >>> + struct pci_dev *pdev = NULL;
> >>> u32 reg, stat;
> >>> int rc;
> >>> @@ -855,10 +857,27 @@ static int amd_poll_link(struct amd_ntb_dev
> *ndev)
> >>> ndev->cntl_sta = reg;
> >>> - rc = pci_read_config_dword(ndev->ntb.pdev,
> >>> - AMD_LINK_STATUS_OFFSET, &stat);
> >>> - if (rc)
> >>> - return 0;
> >>> + if (ndev->ntb.topo == NTB_TOPO_SEC) {
> >>> + /* Locate the pointer to PCIe Root Port for this device */
> >>> + pci_rp = pci_find_pcie_root_port(ndev->ntb.pdev);
> >>> + /* Read the PCIe Link Control and Status register */
> >>> + if (pci_rp) {
> >>> + rc = pcie_capability_read_dword(pci_rp, PCI_EXP_LNKCTL,
> >>> + &stat);
> >>> + if (rc)
> >>> + return 0;
> >>> + }
> >>> + } else if (ndev->ntb.topo == NTB_TOPO_PRI) {
> >>> + /*
> >>> + * For NTB primary, we simply read the Link Status and control
> >>> + * register of the NTB device itself.
> >>> + */
> >>> + pdev = ndev->ntb.pdev;
> >>> + rc = pcie_capability_read_dword(pdev, PCI_EXP_LNKCTL, &stat);
> >>> + if (rc)
> >>> + return 0;
> >>> + }
> >>> +
> >>> ndev->lnk_sta = stat;
> >>> return 1;
> >>> diff --git a/drivers/ntb/hw/amd/ntb_hw_amd.h
> >>> b/drivers/ntb/hw/amd/ntb_hw_amd.h
> >>> index 139a307..39e5d18 100644
> >>> --- a/drivers/ntb/hw/amd/ntb_hw_amd.h
> >>> +++ b/drivers/ntb/hw/amd/ntb_hw_amd.h
> >>> @@ -53,7 +53,6 @@
> >>> #include <linux/pci.h>
> >>> #define AMD_LINK_HB_TIMEOUT msecs_to_jiffies(1000)
> >>> -#define AMD_LINK_STATUS_OFFSET 0x68
> >>> #define NTB_LIN_STA_ACTIVE_BIT 0x00000002
> >>> #define NTB_LNK_STA_SPEED_MASK 0x000F0000
> >>> #define NTB_LNK_STA_WIDTH_MASK 0x03F00000
> >>>
next prev parent reply other threads:[~2019-11-26 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 9:35 [PATCH] NTB: Fix an error in get link status Jiasen Lin
2019-11-17 23:00 ` Jon Mason
2019-11-18 10:17 ` Jiasen Lin
2019-11-20 9:52 ` Jiasen Lin
[not found] ` <CAADLhr7bpb-F0eF1UFXy7AcN=z061mno_QsqGE8z-mvWKvUyCQ@mail.gmail.com>
2019-11-20 14:13 ` Fwd: " Sanjay R Mehta
2019-11-21 13:30 ` Jiasen Lin
2019-11-22 1:27 ` Jiasen Lin
2019-11-26 13:10 ` Sanjay R Mehta
2019-11-26 14:35 ` Nath, Arindam [this message]
2019-12-03 2:54 ` Jiasen Lin
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=MN2PR12MB323225CC169836056288CAA39C450@MN2PR12MB3232.namprd12.prod.outlook.com \
--to=arindam.nath@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=linjiasen007@gmail.com \
--cc=linjiasen@hygon.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.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;
as well as URLs for NNTP newsgroup(s).