linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: mario.limonciello@amd.com, bhelgaas@google.com,
	Aaron Erhardt <aer@tuxedocomputers.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/VGA: Don't assume the only VGA device on a system is `boot_vga`
Date: Sun, 16 Nov 2025 23:20:10 -0600	[thread overview]
Message-ID: <ab9a68fa-bd4e-4c76-afab-b4b7c1713574@kernel.org> (raw)
In-Reply-To: <546c998b-a740-4cc9-8f9c-21c8d2db7c3e@kernel.org>



On 10/29/25 2:38 PM, Mario Limonciello wrote:
> +Thomas
> 
> On 10/29/25 2:34 PM, Bjorn Helgaas wrote:
>> On Wed, Oct 29, 2025 at 01:59:33PM -0500, Mario Limonciello (AMD) wrote:
>>> Some systems ship with multiple display class devices but not all
>>> of them are VGA devices. If the "only" VGA device on the system is not
>>> used for displaying the image on the screen marking it as `boot_vga`
>>> because nothing was found is totally wrong.
>>>
>>> This behavior actually leads to mistakes of the wrong device being
>>> advertised to userspace and then userspace can make incorrect decisions.
>>>
>>> As there is an accurate `boot_display` sysfs file stop lying about
>>> `boot_vga` by assuming if nothing is found it's the right device.
>>>
>>> Reported-by: Aaron Erhardt <aer@tuxedocomputers.com>
>>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220712
>>> Tested-by: Aaron Erhardt <aer@tuxedocomputers.com>
>>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>
>> Do we need a Fixes: here?  A stable cc?
>>
>> The bugzilla suggests this might be a regression and hence v6.18
>> material?
> 
> Yeah I think you're right, we should add these two tags and this should 
> go to 6.18 if it's a reasonable change.
> 
> Cc: stable@vger.kernel.org
> Fixes: ad90860bd10ee ("fbcon: Use screen info to find primary device")
> 
> But let's also make sure Thomas Zimmermann agrees with this change.
> 

ping?

>>
>>> ---
>>>   drivers/pci/vgaarb.c | 7 -------
>>>   1 file changed, 7 deletions(-)
>>>
>>> diff --git a/drivers/pci/vgaarb.c b/drivers/pci/vgaarb.c
>>> index 436fa7f4c3873..baa242b140993 100644
>>> --- a/drivers/pci/vgaarb.c
>>> +++ b/drivers/pci/vgaarb.c
>>> @@ -652,13 +652,6 @@ static bool vga_is_boot_device(struct vga_device 
>>> *vgadev)
>>>           return true;
>>>       }
>>> -    /*
>>> -     * Vgadev has neither IO nor MEM enabled.  If we haven't found any
>>> -     * other VGA devices, it is the best candidate so far.
>>> -     */
>>> -    if (!boot_vga)
>>> -        return true;
>>> -
>>>       return false;
>>>   }
>>> -- 
>>> 2.43.0
>>>
> 
> 


  reply	other threads:[~2025-11-17  5:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 18:59 [PATCH] PCI/VGA: Don't assume the only VGA device on a system is `boot_vga` Mario Limonciello (AMD)
2025-10-29 19:34 ` Bjorn Helgaas
2025-10-29 19:38   ` Mario Limonciello
2025-11-17  5:20     ` Mario Limonciello [this message]
2025-11-17  7:25       ` Thomas Zimmermann
2025-11-17 15:44         ` Bjorn Helgaas
2025-11-17 15:55           ` Mario Limonciello (AMD) (kernel.org)

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=ab9a68fa-bd4e-4c76-afab-b4b7c1713574@kernel.org \
    --to=superm1@kernel.org \
    --cc=aer@tuxedocomputers.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=tzimmermann@suse.de \
    /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).