public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v4] PCI/PTM: Enable PTM only if it advertises a role
Date: Wed, 12 Nov 2025 10:50:01 +0100	[thread overview]
Message-ID: <aRRYSQO9DKo_7ipy@wunner.de> (raw)
In-Reply-To: <20251111153942.GA2174680@bhelgaas>

On Tue, Nov 11, 2025 at 09:39:42AM -0600, Bjorn Helgaas wrote:
> I do wonder about the fact that previously we automatically enabled
> PTM only for Root Ports and Switch Upstream Ports, but we didn't
> enable it for Endpoints until a driver called pci_enable_ptm().
> 
> With this change, it looks like we automatically enable PTM for every
> device that supports it.  Worth a mention in the commit log, and we
> might also want to revisit the drivers (ice, idpf, igc, mlx5) that
> explicitly enable it to remove the enable and disable calls there.
> 
> PTM consumes some link bandwidth, so the idea was to avoid paying that
> cost unless a driver actually wanted to use PTM.

pci_pm_suspend() and pci_pm_runtime_suspend() call pci_suspend_ptm()
and there's a code comment preceding the call that it allows platforms
such as Intel Coffee Lake to go to a deeper power state.

So apparently PTM not only has a bandwidth cost but also a power cost.

Thanks,

Lukas

      parent reply	other threads:[~2025-11-12  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11  6:10 [PATCH v4] PCI/PTM: Enable PTM only if it advertises a role Mika Westerberg
2025-11-11  9:00 ` Lukas Wunner
2025-11-11 15:39 ` Bjorn Helgaas
2025-11-11 15:46   ` Mika Westerberg
2025-11-11 17:04     ` Bjorn Helgaas
2025-11-12  9:50   ` Lukas Wunner [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=aRRYSQO9DKo_7ipy@wunner.de \
    --to=lukas@wunner.de \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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