Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Zhiping Zhang <zhipingz@meta.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	Christian Konig <christian.koenig@amd.com>,
	Alex Williamson <alex@shazbot.org>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wei Huang <wei.huang2@amd.com>
Subject: Re: [PATCH v2] PCI/TPH: fold reserved completer encoding in get_rp_completer_type()
Date: Wed, 15 Jul 2026 18:15:25 -0500	[thread overview]
Message-ID: <20260715231525.GA224907@bhelgaas> (raw)
In-Reply-To: <20260715202409.3767494-1-zhipingz@meta.com>

[+cc Wei, author of f69767a1ada3]

On Wed, Jul 15, 2026 at 01:24:00PM -0700, Zhiping Zhang wrote:
> get_rp_completer_type() returns the Root Port's "TPH Completer
> Supported" field (bits 13:12 of Device Capabilities 2) verbatim. The
> 0b10 encoding is reserved, but pcie_enable_tph() feeds the raw value
> into the requester type:
> 
> 	pdev->tph_req_type = min(pdev->tph_req_type, rp_req_type);
> 
> and later writes tph_req_type to the TPH Requester Enable field, which
> only defines 0b00 (disable), 0b01 (TPH only) and 0b11 (extended TPH).
> If a Root Port ever presents the reserved 0b10, that value could be
> written back to hardware, risking undefined behavior.
> 
> Fold the reserved encoding into "not supported" so only the three
> defined values can propagate.
> 
> Fixes: f69767a1ada3 ("PCI: Add TLP Processing Hints (TPH) support")
> Signed-off-by: Zhiping Zhang <zhipingz@meta.com>
> ---
>  drivers/pci/tph.c | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/tph.c b/drivers/pci/tph.c
> index 655ffd60e62f..ebe1aa5ba5eb 100644
> --- a/drivers/pci/tph.c
> +++ b/drivers/pci/tph.c
> @@ -196,6 +196,21 @@ u16 pcie_tph_get_st_table_size(struct pci_dev *pdev)
>  }
>  EXPORT_SYMBOL(pcie_tph_get_st_table_size);
>  
> +/*
> + * Fold the reserved 0b10 "TPH Completer Supported" encoding into
> + * "not supported" so only the three defined values propagate.
> + */
> +static u8 tph_completer_type_fold(u8 comp)
> +{
> +	switch (comp) {
> +	case PCI_EXP_DEVCAP2_TPH_COMP_TPH_ONLY:
> +	case PCI_EXP_DEVCAP2_TPH_COMP_EXT_TPH:
> +		return comp;
> +	default:
> +		return PCI_EXP_DEVCAP2_TPH_COMP_NONE;
> +	}
> +}
> +
>  /* Return device's Root Port completer capability */
>  static u8 get_rp_completer_type(struct pci_dev *pdev)
>  {
> @@ -211,7 +226,8 @@ static u8 get_rp_completer_type(struct pci_dev *pdev)
>  	if (ret)
>  		return 0;
>  
> -	return FIELD_GET(PCI_EXP_DEVCAP2_TPH_COMP_MASK, reg);
> +	return tph_completer_type_fold(FIELD_GET(PCI_EXP_DEVCAP2_TPH_COMP_MASK,
> +						 reg));

Is this just defensive programming, or is there some hardware out
there that uses this reserved value?  It's kind of an ugly wart to add
just for theoretical spec conformance testing.

If we really need it, I'd rather read something like this:

    tph_comp = FIELD_GET(PCI_EXP_DEVCAP2_TPH_COMP_MASK, reg);
    if (tph_comp == PCI_EXP_DEVCAP2_TPH_COMP_TPH_ONLY ||
	tph_comp == PCI_EXP_DEVCAP2_TPH_COMP_EXT_TPH)
	    return tph_comp;

    return 0;

  parent reply	other threads:[~2026-07-15 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 20:24 [PATCH v2] PCI/TPH: fold reserved completer encoding in get_rp_completer_type() Zhiping Zhang
2026-07-15 20:51 ` sashiko-bot
2026-07-15 23:15 ` Bjorn Helgaas [this message]
2026-07-16  3:50   ` Wei Huang

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=20260715231525.GA224907@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=alex@shazbot.org \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=wei.huang2@amd.com \
    --cc=zhipingz@meta.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