From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Esther Shimanovich <eshimanovich@chromium.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Rajat Jain <rajatja@google.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Lukas Wunner <lukas@wunner.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Detect and trust built-in TBT chips
Date: Thu, 8 Aug 2024 08:22:33 +0300 [thread overview]
Message-ID: <20240808052233.GI1532424@black.fi.intel.com> (raw)
In-Reply-To: <20240806220406.GA80520@bhelgaas>
On Tue, Aug 06, 2024 at 05:04:06PM -0500, Bjorn Helgaas wrote:
> > +static bool pcie_is_tunneled(struct pci_dev *pdev)
> > +{
> > + struct pci_dev *parent, *root;
> > +
> > + parent = pci_upstream_bridge(pdev);
> > + /* If pdev doesn't have a parent, then there's no way it is tunneled.*/
> > + if (!parent)
> > + return false;
> > +
> > + root = pcie_find_root_port(pdev);
> > + /* If pdev doesn't have a root, then there's no way it is tunneled.*/
> > + if (!root)
> > + return false;
> > +
> > + /* Internal PCIe devices are not tunneled. */
> > + if (!root->external_facing)
> > + return false;
> > +
> > + /* Anything directly behind a "usb4-host-interface" is tunneled. */
> > + if (pcie_has_usb4_host_interface(parent))
> > + return true;
> > +
> > + /*
> > + * Check if this is a discrete Thunderbolt/USB4 controller that is
> > + * directly behind the non-USB4 PCIe Root Port marked as
> > + * "ExternalFacingPort". These PCIe devices are used to add Thunderbolt
> > + * capabilities to CPUs that lack integrated Thunderbolt.
> > + * These are not behind a PCIe tunnel.
>
> I need more context to be convinced that this is a reliable heuristic.
> What keeps somebody from plugging a discrete Thunderbolt/USB4
> controller into an external port?
In case of integrated host controller the above function returns true for
anything connected behind its tunneled PCIe root ports so if you plug in
a discrete controller into that it will be treated as tunneled and gets
full IOMMU mappings.
In case of discrete host controller there are two ways. With USB4 the above
function finds "usb4-host-interface" firmware description and returns
true the discrete controller you plug in will be treated as tunneled and
gets full IOMMU mappings.
With non-USB4 (that's Thunderbolt 3 and below) discrete host controller we
have root->external_facing true (it is marked with "ExternalFacingPort"
firmware property) the check below fails because the discrete controller
you plug in is not directly under that so it will be treated as tunneled
and gets full IOMMU mappings.
> Maybe this just needs a sentence or
> two from Lukas's (?) helpful intro to tunneling?
>
> > + if (pcie_switch_directly_under(root, pdev))
> > + return false;
> > +
> > + /* PCIe devices after the discrete chip are tunneled. */
> > + return true;
> > +}
next prev parent reply other threads:[~2024-08-08 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 21:39 [PATCH] PCI: Detect and trust built-in TBT chips Esther Shimanovich
2024-08-06 22:04 ` Bjorn Helgaas
2024-08-07 6:54 ` Mika Westerberg
2024-08-07 21:17 ` Esther Shimanovich
2024-08-08 5:22 ` Mika Westerberg [this message]
2024-08-25 14:57 ` Lukas Wunner
2024-08-07 7:17 ` Mika Westerberg
2024-08-07 21:15 ` Esther Shimanovich
2024-08-08 5:01 ` Mika Westerberg
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=20240808052233.GI1532424@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=eshimanovich@chromium.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael.j.wysocki@intel.com \
--cc=rajatja@google.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