dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: linux-pci@vger.kernel.org
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Joerg Roedel <joro@8bytes.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	iommu@lists.linux.dev, dri-devel@lists.freedesktop.org,
	David Airlie <airlied@redhat.com>
Subject: Re: amd-iommu / agpgart-amd64 problem: Resources present before probing
Date: Wed, 18 Jun 2025 07:27:09 +0200	[thread overview]
Message-ID: <aFJOLZ88KIH5WBy2@wunner.de> (raw)
In-Reply-To: <wpoivftgshz5b5aovxbkxl6ivvquinukqfvb5z6yi4mv7d25ew@edtzr2p74ckg>

On Tue, Jun 17, 2025 at 10:47:48PM +0300, Fedor Pchelkin wrote:
> Hello,
> 
> there is a 
> 
>   [    0.579232] pci 0000:00:00.2: Resources present before probing
> 
> error message observed after
> 
>   commit 3be5fa236649da6404f1bca1491bf02d4b0d5cce
>   Author: Lukas Wunner <lukas@wunner.de>
>   Date:   Fri Apr 25 11:24:21 2025 +0200
>   
>       Revert "iommu/amd: Prevent binding other PCI drivers to IOMMU PCI devices"

For the record, the reporter of the above-quoted issue appears to be
working for an OFAC sanctioned entity:

https://sanctionssearch.ofac.treas.gov/Details.aspx?id=50890

This prohibits me from two-way engagement with the reporter:

https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions

   "Reviewing an unsolicited patch from a contributor in a sanctioned
    region should generally be fine, but actively engaging them to
    better understand their issue, diagnose the problem, or help
    improve a patch or modify code would likely cross the line.
    If the contributor is linked to a sanctioned entity or region,
    in general, it is best to keep communications strictly one-way.
    If a patch is received and you improve it and submit it upstream,
    that should be fine, but going back and forth in communications
    with the SDN developer likely would not."

Hence I am removing the reporter and the lvc-project@linuxtesting.org
address (hosted by ispras.ru) from the To: and Cc: headers.

I note that prior to 6fd024893911, the amd64-agp.c driver was only bound
to devices with a PCI_CAP_ID_AGP capability.

agp_amd64_probe() does check for presence of the capability, but that's
too late to avoid the error message emitted by really_probe().

What we could do however is to first check for presence of a device with
PCI_CAP_ID_AGP, and only if one is found would we try to bind to any
device.  That should avoid the message on any halfway modern system.

Thoughts?

Thanks,

Lukas

      reply	other threads:[~2025-06-18  5:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 19:47 amd-iommu / agpgart-amd64 problem: Resources present before probing Fedor Pchelkin
2025-06-18  5:27 ` Lukas Wunner [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=aFJOLZ88KIH5WBy2@wunner.de \
    --to=lukas@wunner.de \
    --cc=airlied@redhat.com \
    --cc=ben@decadent.org.uk \
    --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 \
    /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).