From: Lukas Wunner <lukas@wunner.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
David Airlie <airlied@redhat.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Andi Kleen <ak@linux.intel.com>, Ahmed Salem <x0rw3ll@gmail.com>,
Borislav Petkov <bp@alien8.de>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] agp/amd64: Bind to unsupported devices only if AGP is present
Date: Wed, 25 Jun 2025 16:33:31 +0200 [thread overview]
Message-ID: <aFwIu0QveVuJZNoU@wunner.de> (raw)
In-Reply-To: <98012c55-1e0d-4c1b-b650-5bb189d78009@redhat.com>
On Wed, Jun 25, 2025 at 04:08:38PM +0200, Hans de Goede wrote:
> Lukas made me aware of this attempt to fix the KERN_CRIT msg, because
> I wrote a slightly different patch to fix this:
>
> https://lore.kernel.org/dri-devel/20250625112411.4123-1-hansg@kernel.org/
>
> This seems like a cleaner fix to me and something which would be good
> to have regardless since currently the driver_attach() call is doing
> too much work because the promisc table catches an unnecessary wide
> net / match matching many PCI devices which cannot be AGP capable
> at all.
So how do you know that all of these unsupported devices have
PCI_CLASS_BRIDGE_HOST? The only thing we know is that an AGP
Capability must be present.
In particular, AGP 3.0 sec 2.5 explicitly allows PCI-to-PCI bridges
in addition to Host-to-PCI bridges.
Thanks,
Lukas
next prev parent reply other threads:[~2025-06-25 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 9:40 [PATCH] agp/amd64: Bind to unsupported devices only if AGP is present Lukas Wunner
2025-06-21 12:07 ` Ben Hutchings
2025-06-21 12:29 ` Lukas Wunner
2025-06-21 13:51 ` Ben Hutchings
2025-06-21 14:05 ` Lukas Wunner
2025-06-24 21:54 ` Ben Hutchings
2025-06-25 14:08 ` Hans de Goede
2025-06-25 14:33 ` Lukas Wunner [this message]
2025-06-25 18:43 ` Hans de Goede
2025-06-30 11:10 ` Hans de Goede
2025-07-02 10:47 ` Lukas Wunner
2025-07-02 13:29 ` Lukas Wunner
2025-07-01 18:28 ` Lukas Wunner
2025-07-02 15:24 ` Lukas Wunner
2025-07-01 18:18 ` Lukas Wunner
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=aFwIu0QveVuJZNoU@wunner.de \
--to=lukas@wunner.de \
--cc=airlied@redhat.com \
--cc=ak@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=x0rw3ll@gmail.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