Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221108222944.GA504625@bhelgaas> <20221109173454.GA567052@bhelgaas>
In-Reply-To: <20221109173454.GA567052@bhelgaas>
From:   Nathan Rossi <nathan@nathanrossi.com>
Date:   Mon, 14 Nov 2022 13:59:56 +1000
Message-ID: <CA+aJhH2EEE_n5T0PAcOr5RQbfOzEKF67ckcWMTbP_NesQ5ggtw@mail.gmail.com>
Subject: Re: [PATCH] PCI/ASPM: Wait for data link active after retraining
To:     Bjorn Helgaas <helgaas@kernel.org>
Cc:     linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
        Nathan Rossi <nathan.rossi@digi.com>,
        Bjorn Helgaas <bhelgaas@google.com>,
        "Maciej W. Rozycki" <macro@orcam.me.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, 10 Nov 2022 at 03:34, Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> [+cc Maciej for similar retrain issue]
>
> On Tue, Nov 08, 2022 at 04:29:44PM -0600, Bjorn Helgaas wrote:
> > On Thu, Jun 02, 2022 at 06:55:44AM +0000, Nathan Rossi wrote:
> > > From: Nathan Rossi <nathan.rossi@digi.com>
> > >
> > > When retraining the link either the child or the parent device may ha=
ve
> > > the data link layer state machine of the respective devices move out =
of
> > > the active state despite the physical link training being completed.
> > > Depending on how long is takes for the devices to return to the activ=
e
> > > state, the device may not be ready and any further reads/writes to th=
e
> > > device can fail.
> > >
> > > This issue is present with the pci-mvebu controller paired with a dev=
ice
> > > supporting ASPM but without advertising the Slot Clock, where during
> > > boot the pcie_aspm_cap_init call would cause common clocks to be made
> > > consistent and then retrain the link. However the data link layer wou=
ld
> > > not be active before any device initialization (e.g. ASPM capability
> > > queries, BAR configuration) causing improper configuration of the dev=
ice
> > > without error.
> > >
> > > To ensure the child device is accessible, after the link retraining u=
se
> > > pcie_wait_for_link to perform the associated state checks and any nee=
ded
> > > delays.
> > >
> > > Signed-off-by: Nathan Rossi <nathan.rossi@digi.com>
> > > ---
> > >  drivers/pci/pcie/aspm.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> > > index a96b7424c9..4b8a1810be 100644
> > > --- a/drivers/pci/pcie/aspm.c
> > > +++ b/drivers/pci/pcie/aspm.c
> > > @@ -288,7 +288,8 @@ static void pcie_aspm_configure_common_clock(stru=
ct pcie_link_state *link)
> > >             reg16 &=3D ~PCI_EXP_LNKCTL_CCC;
> > >     pcie_capability_write_word(parent, PCI_EXP_LNKCTL, reg16);
> > >
> > > -   if (pcie_retrain_link(link))
> > > +   /* Retrain link and then wait for the link to become active */
> > > +   if (pcie_retrain_link(link) && pcie_wait_for_link(parent, true))
> >
> > pcie_retrain_link() waits for PCI_EXP_LNKSTA_LT (Link Training) to be
> > cleared, which means the LTSSM has exited the Configuration/Recovery
> > state.  pcie_wait_for_link() waits for PCI_EXP_LNKSTA_DLLLA (Data Link
> > Layer Link Active) to be set, which means the link is in DL_Active.
> >
> > I don't see an explicit procedure in the spec for determining when
> > a link retrain is complete, but from PCIe r6.0, sec 6.2.11 (DPC):
> >
> >   After software releases the Downstream Port from DPC, the Port=E2=80=
=99s
> >   LTSSM must transition to the Detect state, where the Link will
> >   attempt to retrain. Software can use Data Link Layer State Changed
> >   interrupts, DL_ACTIVE ERR_COR signaling, or both, to signal when the
> >   Link reaches the DL_Active state again.
> >
> > and sec 6.6:
> >
> >   On the completion of Link Training (entering the DL_Active state,
> >   see Section 3.2), a component must be able to receive and process
> >   TLPs and DLLPs.
> >
> > The only use mentioned in the spec for the Link Training bit is the
> > implementation note in sec 7.5.3.7 about avoiding race conditions when
> > using the Retrain Link bit, where software should poll Link Training
> > until it returns to zero before setting the Retrain Link bit to change
> > link parameters.
> >
> > And I think you're absolutely right that what we *want* here is the
> > data link layer DL_Active state, not just the link layer L0 state.
> >
> > This all makes me think that checking the Link Training bit might be
> > the wrong thing to begin with.
> >
> > Of course, the Data Link Layer Link Active bit wasn't added until PCIe
> > r1.1, and even now it's optional.  Without it, I don't know if there's
> > a way to make sure the link is in DL_Active.

My understanding is there is no way to check for the DL_Active state
on these devices. Which is why pcie_wait_for_link_delay uses a fixed
delay in that case.

> >
> > Maybe pcie_retrain_link() should wait for Data Link Layer Link Active
> > if it is supported, and use the existing behavior of waiting for Link
> > Training to be cleared otherwise?

I think it still makes sense for pcie_retrain_link to wait for the
Link Training bit, since it is typical for the retraining to never go
to a LTSSM state where the LinkUp is 0 (e.g. Recovery ->
Configuration), thus the Data Link Layer will stay in DL_Active. But
it is still important to wait for the link training to complete in
that case, but also because the training may not cause the Data Link
state to change immediately.

However since DLLLA reporting is optional, it is probably ideal if the
pcie_retrain_link only calls pcie_wait_for_link if reporting is
available? This would avoid the fixed delay of 1s upon link retraining
for devices without reporting, which is unnecessary in the majority of
cases.

Thanks,
Nathan


>
> Nathan, I meant to cc you on this thread, which is doing something
> very similar.  Just FYI:
>
> https://lore.kernel.org/all/alpine.DEB.2.21.2209130050380.60554@angie.orc=
am.me.uk/