linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] pci: Fixes MaxPayloadSize (MPS) programming for RCiEP devices.
Date: Thu, 14 May 2020 18:27:46 -0500	[thread overview]
Message-ID: <20200514232746.GA478643@bjorn-Precision-5520> (raw)
In-Reply-To: <1585343775-4019-1-git-send-email-ashok.raj@intel.com>

On Fri, Mar 27, 2020 at 02:16:15PM -0700, Ashok Raj wrote:
> Root Complex Integrated devices (RCiEP) do not have a Root Port before the
> device. pci_configure_mps() should simply stick the max value for MaxPayload
> size in Device Control, and for MaxReadReq. Unless pcie=pcie_bus-peer2peer
> is used in kernel commandline PCIE_BUS_PEER2PEER.
> 
> When MPS is configured lower, it could result in reduced performance.
> 
> Fixes: 9dae3a97297f ("PCI: Move MPS configuration check to pci_configure_device()")
> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> Tested-by: Dave Jiang <dave.jiang@intel.com>
> To: Bjorn Helgaas <bhelgaas@google.com>
> To: linux-pci@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: stable@vger.kernel.org
> Cc: Ashok Raj <ashok.raj@intel.com>

Applied to pci/enumeration for v5.8, thanks!

> ---
>  drivers/pci/probe.c | 23 ++++++++++++++++++++++-
>  1 file changed, 22 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index eeff8a07..a738b1c 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1895,13 +1895,34 @@ static void pci_configure_mps(struct pci_dev *dev)
>  	struct pci_dev *bridge = pci_upstream_bridge(dev);
>  	int mps, mpss, p_mps, rc;
>  
> -	if (!pci_is_pcie(dev) || !bridge || !pci_is_pcie(bridge))
> +	if (!pci_is_pcie(dev))
>  		return;
>  
>  	/* MPS and MRRS fields are of type 'RsvdP' for VFs, short-circuit out */
>  	if (dev->is_virtfn)
>  		return;
>  
> +	/*
> +	 * If this is a Root Complex Integrated Endpoint
> +	 * Simply program the max value from DEVCAP. No additional
> +	 * Lookup is necessary
> +	 */
> +	if (pci_pcie_type(dev) == PCI_EXP_TYPE_RC_END) {
> +		if (pcie_bus_config == PCIE_BUS_PEER2PEER)
> +			mps = 128;
> +		else
> +			mps = 128 << dev->pcie_mpss;
> +		rc = pcie_set_mps(dev, mps);
> +		if (rc) {
> +			pci_warn(dev, "can't set Max Payload Size to %d; if necessary, use \"pci=pcie_bus_safe\" and report a bug\n",
> +			 mps);
> +			return;
> +		}
> +	}
> +
> +	if (!bridge || !pci_is_pcie(bridge))
> +		return;
> +
>  	mps = pcie_get_mps(dev);
>  	p_mps = pcie_get_mps(bridge);
>  
> -- 
> 2.7.4
> 

      parent reply	other threads:[~2020-05-14 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 21:16 [PATCH] pci: Fixes MaxPayloadSize (MPS) programming for RCiEP devices Ashok Raj
2020-03-31 13:11 ` Sasha Levin
2020-05-14 23:27 ` Bjorn Helgaas [this message]

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=20200514232746.GA478643@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=ashok.raj@intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).