From: Lukas Wunner <lukas@wunner.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 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: Sat, 21 Jun 2025 14:29:33 +0200 [thread overview]
Message-ID: <aFalrV1500saBto5@wunner.de> (raw)
In-Reply-To: <b73fbb3e3f03d842f36e6ba2e6a8ad0bb4b904fd.camel@decadent.org.uk>
On Sat, Jun 21, 2025 at 02:07:40PM +0200, Ben Hutchings wrote:
> On Sat, 2025-06-21 at 11:40 +0200, Lukas Wunner wrote:
> > Since commit 172efbb40333 ("AGP: Try unsupported AGP chipsets on x86-64 by
> > default"), the AGP driver for AMD Opteron/Athlon64 CPUs attempts to bind
> > to any PCI device.
> >
> > On modern CPUs exposing an AMD IOMMU, this results in a message with
> > KERN_CRIT severity:
> >
> > pci 0000:00:00.2: Resources present before probing
> >
> > The driver used to bind only to devices exposing the AGP Capability, but
> > that restriction was removed by commit 6fd024893911 ("amd64-agp: Probe
> > unknown AGP devices the right way").
>
> That didn't remove any restriction as the probe function still started
> by checking for an AGP capability. The change I made was that the
> driver would actually bind to devices with the AGP capability instead of
> starting to use them without binding.
The message above would not be emitted without your change.
The check for the AGP capability in agp_amd64_probe() is too late
to prevent the message. That's because the message is emitted
before ->probe() is even called.
Thanks,
Lukas
next prev parent reply other threads:[~2025-06-21 12:29 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 [this message]
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
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=aFalrV1500saBto5@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=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