linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, alex.williamson@redhat.com
Cc: Wilson.Snyder@cavium.com, Vadim.Lomovtsev@cavium.com
Subject: Re: [PATCH v4] PCI: quirks: update Cavium ThunderX ACS quirk implementation
Date: Wed, 20 Sep 2017 04:33:21 -0700	[thread overview]
Message-ID: <20170920113321.GA32496@localhost.localdomain> (raw)
In-Reply-To: <1505724481-28413-1-git-send-email-Vadim.Lomovtsev@caviumnetworks.com>

Hi guys,

Sorry for annoying topic ..
Could you please provide your comments/objections on this if any ?

WBR,
Vadim

On Mon, Sep 18, 2017 at 01:48:01AM -0700, Vadim Lomovtsev wrote:
> This commit makes Cavium PCI ACS quirk applicable only to Cavium
> ThunderX (CN81/83/88XX) PCIE Root Ports which has limited PCI capabilities
> in terms of no ACS support advertisement. However, the RTL internally
> implements similar protection as if ACS had completion/request redirection,
> upstream forwarding and validation features enabled.
> 
> Current quirk implementation doesn't take into account PCIERCs which
> also needs to be quirked. So the pci device id check mask is updated
> and check of device ID moved into separate function.
> 
> Signed-off-by: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
> ---
> 	v1	: put device check into separate function and extend it to all
> 		  Cavium PCIERC/PCCBR devices;
> 	v1 -> v2: update match function in order to filter only ThunderX devices by device
> 	      	  ids to properly filter CN8XXX devices, update subject & description with
> 		  ACS register info (rejected by maillist due to triple X in subject);
> 	v2 -> v3: update subject: remove CN8XXX from subject line, replace it with ThunderX;
> 	v3 -> v4: update ACS mask (remove TB and TD bits), update commit message (remove
> 	      	  ACS register printout);
> 
>  drivers/pci/quirks.c | 26 ++++++++++++++++----------
>  1 file changed, 16 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index a4d3361..e6b904a 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4211,20 +4211,26 @@ static int pci_quirk_amd_sb_acs(struct pci_dev *dev, u16 acs_flags)
>  #endif
>  }
>  
> -static int pci_quirk_cavium_acs(struct pci_dev *dev, u16 acs_flags)
> +/*
> + * Cavium devices matching this quirk do not perform peer-to-peer
> + * with other functions, allowing masking out these bits as if they
> + * were unimplemented in the ACS capability.
> + */
> +#define CAVIUM_CN8XXX_ACS_FLAGS (PCI_ACS_RR | PCI_ACS_CR | PCI_ACS_SV | PCI_ACS_UF)
> +
> +static __inline__  bool pci_quirk_cavium_acs_match(struct pci_dev *dev)
>  {
> -	/*
> -	 * Cavium devices matching this quirk do not perform peer-to-peer
> -	 * with other functions, allowing masking out these bits as if they
> -	 * were unimplemented in the ACS capability.
> -	 */
> -	acs_flags &= ~(PCI_ACS_SV | PCI_ACS_TB | PCI_ACS_RR |
> -		       PCI_ACS_CR | PCI_ACS_UF | PCI_ACS_DT);
> +	return (pci_is_pcie(dev) &&
> +		(pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT) &&
> +		((dev->device & 0xf800) == 0xa000));
> +}
>  
> -	if (!((dev->device >= 0xa000) && (dev->device <= 0xa0ff)))
> +static int pci_quirk_cavium_acs(struct pci_dev *dev, u16 acs_flags)
> +{
> +	if (!pci_quirk_cavium_acs_match(dev))
>  		return -ENOTTY;
>  
> -	return acs_flags ? 0 : 1;
> +	return acs_flags & ~(CAVIUM_CN8XXX_ACS_FLAGS) ? 0 : 1;
>  }
>  
>  static int pci_quirk_xgene_acs(struct pci_dev *dev, u16 acs_flags)
> -- 
> 2.9.5
> 

  reply	other threads:[~2017-09-20 11:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 11:55 [PATCH] PCI: quirks: update cavium ACS quirk implementation Vadim Lomovtsev
2017-09-12 16:15 ` Alex Williamson
2017-09-13 11:37   ` Vadim Lomovtsev
2017-09-13 12:01   ` Vadim Lomovtsev
2017-09-15 12:57 ` [PATCH v3] PCI: quirks: update Cavium ThunderX " Vadim Lomovtsev
2017-09-15 19:20   ` Lomovtsev, Vadim
2017-09-18  8:48   ` [PATCH v4] " Vadim Lomovtsev
2017-09-20 11:33     ` Vadim Lomovtsev [this message]
2017-09-20 16:31     ` Alex Williamson
2017-09-21  8:39       ` Vadim Lomovtsev
2017-09-25 13:08     ` [PATCH v5] " Vadim Lomovtsev
2017-09-26 15:23       ` Vadim Lomovtsev
2017-09-26 15:43       ` Alex Williamson
2017-09-26 16:00         ` Vadim Lomovtsev
2017-09-27 18:03           ` Vadim Lomovtsev
2017-09-27 18:20       ` [PATCH v6] " Vadim Lomovtsev
2017-09-27 20:03         ` Vadim Lomovtsev
2017-09-27 20:18         ` Alex Williamson
2017-09-29 12:22           ` Vadim Lomovtsev
2017-10-09 16:14           ` Vadim Lomovtsev
2017-10-12 13:27         ` Robert Richter
2017-10-16 21:23         ` Bjorn Helgaas
2017-10-17 11:29           ` Vadim Lomovtsev
2017-10-17 12:47         ` [PATCH v7 0/2] PCI: quirks: Cavium ThunderX ACS quirk update Vadim Lomovtsev
2017-10-17 12:47           ` [PATCH v7 1/2] PCI: quirks: Set Cavium ACS capability quirk flags to assert RR/CR/SV/UF Vadim Lomovtsev
2017-10-17 12:47           ` [PATCH v7 2/2] PCI: quirks: Apply Cavium ThunderX ACS quirk only to Root Ports Vadim Lomovtsev
2017-10-19 11:26           ` [PATCH v7 0/2] PCI: quirks: Cavium ThunderX ACS quirk update Bjorn Helgaas
2017-10-19 11:59             ` Vadim Lomovtsev
2017-10-19 18:50               ` Bjorn Helgaas
2017-10-20 10:44                 ` Vadim Lomovtsev

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=20170920113321.GA32496@localhost.localdomain \
    --to=vadim.lomovtsev@caviumnetworks.com \
    --cc=Vadim.Lomovtsev@cavium.com \
    --cc=Wilson.Snyder@cavium.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).