linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Håkon Bugge" <haakon.bugge@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Sinan Kaya <okaya@codeaurora.org>,
	 linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Do not attempt to set ExtTag for VFs
Date: Tue, 11 Nov 2025 15:30:50 +0200 (EET)	[thread overview]
Message-ID: <dc6f1dc8-a2e7-d48f-49a2-ee6e0288e672@linux.intel.com> (raw)
In-Reply-To: <20251111132401.1827922-1-haakon.bugge@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

On Tue, 11 Nov 2025, Håkon Bugge wrote:

> The bit for enabling extended tags is Reserved and Preserved (RsvdP)
> for VFs.

Please add a PCIe spec reference.

> Hence, bail out early from pci_configure_extended_tags() if
> the device is a VF.
> 
> Otherwise, we may see incorrect log messages such as:
> 
> 	   kernel: pci 0000:af:00.2: enabling Extended Tags
> 
> (af:00.2 is a VF)
> 
> Fixes: 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported")
> Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
> ---
>  drivers/pci/probe.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 0ce98e18b5a87..014017e15bcc8 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -2244,7 +2244,8 @@ int pci_configure_extended_tags(struct pci_dev *dev, void *ign)
>  	u16 ctl;
>  	int ret;
>  
> -	if (!pci_is_pcie(dev))
> +	/* PCI_EXP_DEVCTL_EXT_TAG is RsvdP in VFs */
> +	if (!pci_is_pcie(dev) || dev->is_virtfn)
>  		return 0;
>  
>  	ret = pcie_capability_read_dword(dev, PCI_EXP_DEVCAP, &cap);
> 

-- 
 i.

      reply	other threads:[~2025-11-11 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11 13:24 [PATCH] PCI: Do not attempt to set ExtTag for VFs Håkon Bugge
2025-11-11 13:30 ` Ilpo Järvinen [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=dc6f1dc8-a2e7-d48f-49a2-ee6e0288e672@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=haakon.bugge@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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).