From: Steven J Abner <pheonix.sja@att.net>
To: linux-kernel@vger.kernel.org
Subject: amd iommu configuration
Date: Thu, 01 Sep 2022 14:36:20 -0400 [thread overview]
Message-ID: <KONJHR.T3DS4EBAXDVX1@att.net> (raw)
In-Reply-To: <KONJHR.T3DS4EBAXDVX1.ref@att.net>
Hi
Building a kernel tailored for AMD 2400g on ASRock B450 using 5.18.12
as base.
I stumbled across an odd situation and which lacked Kconfig info and
lead to oddity.
/drivers/iommu/amd/Kconfig states 'config AMD_IOMMU_V2' is 'tristate'
but unlike many
other tristate configures doesn't mention that module name is
'iommu_v2.ko' and loading should be done by adding to modules-load.d.
The oddity is that by loading as module is as follows (differences):
builtin iommu_v2 version dmesg:
amdgpu: HMM registered 2048MB device memory
amdgpu: Topology: Add APU node [0x0:0x0]
amdgpu: Topology: Add APU node [0x15dd:0x1002]
AMD-Vi: AMD IOMMUv2 loaded and initialized
kfd kfd: amdgpu: added device 1002:15dd
kfd kfd: amdgpu: Allocated 3969056 bytes on gart
memmap_init_zone_device initialised 524288 pages in 0ms
module not loaded due to missing iommu.conf dmesg:
amdgpu: CRAT table disabled by module option
amdgpu: Topology: Add CPU node
amdgpu: Virtual CRAT table created for CPU
kfd kfd: amdgpu: GC IP 090100 not supported in kfd
module load through iommu.conf dmesg:
amdgpu: CRAT table disabled by module option
amdgpu: Topology: Add CPU node
amdgpu: Virtual CRAT table created for CPU
AMD-Vi: AMD IOMMUv2 loaded and initialized
kfd kfd: amdgpu: GC IP 090100 not supported in kfd
Note, only difference on witk/without iommu.conf is:
AMD-Vi: AMD IOMMUv2 loaded and initialized
So does this mean missing features by not having builtin?
If not, should Kconfig have hint about module and loading?
Steve
I wish to be personally CC'ed the answers/comments posted to the list
in response to my posting, please:) Not a list member.
next parent reply other threads:[~2022-09-01 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <KONJHR.T3DS4EBAXDVX1.ref@att.net>
2022-09-01 18:36 ` Steven J Abner [this message]
2022-09-02 22:10 ` Randy Dunlap
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=KONJHR.T3DS4EBAXDVX1@att.net \
--to=pheonix.sja@att.net \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®