Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Lu Baolu" <baolu.lu@linux.intel.com>,
	"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux.dev>,
	"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
	"open list:VFIO DRIVER" <kvm@vger.kernel.org>,
	"open list:SOUND" <linux-sound@vger.kernel.org>,
	"Daniel Dadap" <ddadap@nvidia.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>
Subject: Re: [PATCH v5 9/9] PCI: Add a new 'boot_display' attribute
Date: Fri, 27 Jun 2025 11:15:52 -0500	[thread overview]
Message-ID: <20250627161552.GA1671755@bhelgaas> (raw)
In-Reply-To: <5cc01163-1feb-4a18-8060-27f4da39b2e4@kernel.org>

On Thu, Jun 26, 2025 at 06:33:15PM -0500, Mario Limonciello wrote:
> On 6/26/25 4:47 PM, Bjorn Helgaas wrote:
> > On Thu, Jun 26, 2025 at 04:12:21PM -0500, Mario Limonciello wrote:
> > > On 6/26/2025 3:45 PM, Bjorn Helgaas wrote:
> > > > On Tue, Jun 24, 2025 at 03:30:42PM -0500, Mario Limonciello wrote:
> > > > > From: Mario Limonciello <mario.limonciello@amd.com>
> > > > > 
> > > > > On systems with multiple GPUs there can be uncertainty which GPU is the
> > > > > primary one used to drive the display at bootup. In order to disambiguate
> > > > > this add a new sysfs attribute 'boot_display' that uses the output of
> > > > > video_is_primary_device() to populate whether a PCI device was used for
> > > > > driving the display.
> > > > > 
> > > > > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > > > 
> > > > Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > > > 
> > > > Question below.
> > > > 
> > > > > ---
> > > > > v4:
> > > > >    * new patch
> > > > > ---
> > > > >    Documentation/ABI/testing/sysfs-bus-pci |  9 +++++++++
> > > > >    drivers/pci/pci-sysfs.c                 | 14 ++++++++++++++
> > > > >    2 files changed, 23 insertions(+)
> > > > > 
> > > > > diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
> > > > > index 69f952fffec72..897cfc1b0de0f 100644
> > > > > --- a/Documentation/ABI/testing/sysfs-bus-pci
> > > > > +++ b/Documentation/ABI/testing/sysfs-bus-pci
> > > > > @@ -612,3 +612,12 @@ Description:
> > > > >    		  # ls doe_features
> > > > >    		  0001:01        0001:02        doe_discovery
> > > > > +
> > > > > +What:		/sys/bus/pci/devices/.../boot_display
> > > > > +Date:		October 2025
> > > > > +Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
> > > > > +Description:
> > > > > +		This file indicates whether the device was used as a boot
> > > > > +		display. If the device was used as the boot display, the file
> > > > > +		will contain "1". If the device is a display device but wasn't
> > > > > +		used as a boot display, the file will contain "0".
> > > > 
> > > > Is there a reason to expose this file if it wasn't a boot display
> > > > device?  Maybe it doesn't need to exist at all unless it contains "1"?
> > > 
> > > I was mostly thinking that it's a handy way for userspace to know whether
> > > the kernel even supports this feature.  If userspace sees that file on any
> > > GPU as it walks a list then it knows it can use that for a hint.
> > > 
> > > But if you would rather it only shows up for the boot display yes it's
> > > possible to do I think.  It's just more complexity to the visibility lookup
> > > to also call video_is_primary_device().
> > 
> > I think for a singleton situation like this it makes more sense to
> > only expose the file for one device, not several files where only one
> > of them contains "1".
> 
> I did an experiment with this but the PCI resources aren't ready at the time
> visibility is determined.
> 
> So either:
> * the sysfs file creation needs to be deferred similar to
> pci_create_resource_files() does
> 
> or
> 
> * call to sysfs_update_group() is needed to recalculate visibility.

Sigh, yeah, that's an old annoying problem.  I think deferring as you
did is fine.

> > > > > diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
> > > > > index 268c69daa4d57..5bbf79b1b953d 100644
> > > > > --- a/drivers/pci/pci-sysfs.c
> > > > > +++ b/drivers/pci/pci-sysfs.c
> > > > > @@ -30,6 +30,7 @@
> > > > >    #include <linux/msi.h>
> > > > >    #include <linux/of.h>
> > > > >    #include <linux/aperture.h>
> > > > > +#include <asm/video.h>
> > > > >    #include "pci.h"
> > > > >    #ifndef ARCH_PCI_DEV_GROUPS
> > > > > @@ -679,6 +680,13 @@ const struct attribute_group *pcibus_groups[] = {
> > > > >    	NULL,
> > > > >    };
> > > > > +static ssize_t boot_display_show(struct device *dev, struct device_attribute *attr,
> > > > > +				 char *buf)
> > > > > +{
> > > > > +	return sysfs_emit(buf, "%u\n", video_is_primary_device(dev));
> > > > > +}
> > > > > +static DEVICE_ATTR_RO(boot_display);
> > > > > +
> > > > >    static ssize_t boot_vga_show(struct device *dev, struct device_attribute *attr,
> > > > >    			     char *buf)
> > > > >    {
> > > > > @@ -1698,6 +1706,7 @@ late_initcall(pci_sysfs_init);
> > > > >    static struct attribute *pci_dev_dev_attrs[] = {
> > > > >    	&dev_attr_boot_vga.attr,
> > > > > +	&dev_attr_boot_display.attr,
> > > > >    	NULL,
> > > > >    };
> > > > > @@ -1710,6 +1719,11 @@ static umode_t pci_dev_attrs_are_visible(struct kobject *kobj,
> > > > >    	if (a == &dev_attr_boot_vga.attr && pci_is_vga(pdev))
> > > > >    		return a->mode;
> > > > > +#ifdef CONFIG_VIDEO
> > > > > +	if (a == &dev_attr_boot_display.attr && pci_is_display(pdev))
> > > > > +		return a->mode;
> > > > > +#endif
> > > > > +
> > > > >    	return 0;
> > > > >    }
> > > > > -- 
> > > > > 2.43.0
> > > > > 
> > > 
> 

      reply	other threads:[~2025-06-27 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 20:30 [PATCH v5 0/9] Adjust fbcon console device detection Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 1/9] PCI: Add helper for checking if a PCI device is a display controller Mario Limonciello
2025-06-26 20:43   ` Bjorn Helgaas
2025-06-26 21:14     ` Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 2/9] vfio/pci: Use pci_is_display() Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 3/9] vga_switcheroo: " Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 4/9] iommu/vt-d: " Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 5/9] ALSA: hda: " Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 6/9] Fix access to video_is_primary_device() when compiled without CONFIG_VIDEO Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 7/9] PCI/VGA: Replace vga_is_firmware_default() with a screen info check Mario Limonciello
2025-06-25  9:38   ` kernel test robot
2025-06-26 20:45   ` Bjorn Helgaas
2025-06-24 20:30 ` [PATCH v5 8/9] fbcon: Use screen info to find primary device Mario Limonciello
2025-06-24 20:30 ` [PATCH v5 9/9] PCI: Add a new 'boot_display' attribute Mario Limonciello
2025-06-26 20:45   ` Bjorn Helgaas
2025-06-26 21:12     ` Mario Limonciello
2025-06-26 21:47       ` Bjorn Helgaas
2025-06-26 23:33         ` Mario Limonciello
2025-06-27 16:15           ` Bjorn Helgaas [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=20250627161552.GA1671755@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=ddadap@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mario.limonciello@amd.com \
    --cc=mripard@kernel.org \
    --cc=perex@perex.cz \
    --cc=robin.murphy@arm.com \
    --cc=simona@ffwll.ch \
    --cc=superm1@kernel.org \
    --cc=tiwai@suse.com \
    --cc=tzimmermann@suse.de \
    --cc=will@kernel.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