Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Sathyanarayanan Kuppuswamy 
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI/portdrv: Do not require an interrupt for all AER capable ports
Date: Thu, 8 Dec 2022 06:23:49 -0600	[thread overview]
Message-ID: <20221208122349.GA1525911@bhelgaas> (raw)
In-Reply-To: <Y5F9EnsNqyc3hEeK@black.fi.intel.com>

On Thu, Dec 08, 2022 at 07:58:42AM +0200, Mika Westerberg wrote:
> On Wed, Dec 07, 2022 at 04:35:37PM -0600, Bjorn Helgaas wrote:
> > On Wed, Dec 07, 2022 at 10:41:05AM +0200, Mika Westerberg wrote:
> > > Only Root Ports and Event Collectors use MSI for AER. PCIe Switch ports
> > > or endpoints on the other hand only send messages (that get collected by
> > > the former). For this reason do not require PCIe switch ports and
> > > endpoints to use interrupt if they support AER.
> > > 
> > > This allows portdrv to attach PCIe switch ports of Intel DG1 and DG2
> > > discrete graphics cards. These do not declare MSI or legacy interrupts.
> > 
> > Help me understand more about this situation.  I guess we want portdrv
> > to attach not to a GPU itself, but to a switch port on the card that
> > *leads* to the GPU?
> 
> Yes correct.
> 
> > From the patch, it looks like the only PCIe port service this switch
> > port advertises is AER (not PME, DPC, hotplug, etc), and it doesn't
> > have MSI or MSI-X.
> 
> Correct.
> 
> > So aerdriver should be able to register for PCIE_PORT_SERVICE_AER, but
> > aer_probe() ignores everything except Root Ports and RCECs.  What's
> > the benefit then?  I must be missing something.
> 
> The portdrv is needed for power management and everything else PCI even
> if there is no actual "service" attached.

Thanks!  I'm trying to connect the dots to get to the specific bug fix
or improvement made by this patch.

The pcie_pme_driver itself doesn't seem involved because it registers
for PCIE_PORT_SERVICE_PME, and that's only set for Root Ports and
RCECs.

The pcie_portdrv_pm_ops would be another possibility, but with the
exception of pcie_port_runtime_idle(), all those ops just iterate over
service drivers, which aren't involved.

So I'm guessing this has to do with setting
DPM_FLAG_NO_DIRECT_COMPLETE and DPM_FLAG_SMART_SUSPEND in
pcie_portdrv_probe().  Does the lack of portdrv mean the GPU can't
suspend?  Does this reduce power consumption?  How would a user know
this change would help their system?

Bjorn

  reply	other threads:[~2022-12-08 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:41 [PATCH v2] PCI/portdrv: Do not require an interrupt for all AER capable ports Mika Westerberg
2022-12-07 14:31 ` Sathyanarayanan Kuppuswamy
2022-12-07 22:35 ` Bjorn Helgaas
2022-12-08  5:58   ` Mika Westerberg
2022-12-08 12:23     ` Bjorn Helgaas [this message]
2022-12-08 13:58       ` Mika Westerberg
2022-12-08 14:12         ` Mika Westerberg
2022-12-09 17:07 ` Bjorn Helgaas
2022-12-09 21:04   ` Sathyanarayanan Kuppuswamy
2022-12-09 21:48     ` Bjorn Helgaas
2022-12-09 22:13       ` Sathyanarayanan Kuppuswamy

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=20221208122349.GA1525911@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=sathyanarayanan.kuppuswamy@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