Message ID | b0b8c35f-5c88-46bb-a882-9ff737683367@suse.com (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | AMD/IOMMU: assorted corrections | expand |
On 2025-01-30 06:13, Jan Beulich wrote: > Despite all the verbosity with "iommu=debug", information on the IOMMUs > themselves was missing. > > Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Jason Andryuk <jason.andryuk@amd.com> Tested-by: Jason Andryuk <jason.andryuk@amd.com> Thanks, Jason
On 30/01/2025 11:13 am, Jan Beulich wrote: > Despite all the verbosity with "iommu=debug", information on the IOMMUs > themselves was missing. > > Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
--- a/xen/drivers/passthrough/amd/iommu_acpi.c +++ b/xen/drivers/passthrough/amd/iommu_acpi.c @@ -911,6 +911,11 @@ static int __init parse_ivhd_block(const return -ENODEV; } + AMD_IOMMU_DEBUG("IVHD: IOMMU @ %#lx cap @ %#x seg 0x%04x info %#x attr %#x\n", + ivhd_block->base_address, ivhd_block->capability_offset, + ivhd_block->pci_segment_group, ivhd_block->info, + ivhd_block->iommu_attr); + iommu = find_iommu_from_bdf_cap(ivhd_block->pci_segment_group, ivhd_block->header.device_id, ivhd_block->capability_offset);
Despite all the verbosity with "iommu=debug", information on the IOMMUs themselves was missing. Signed-off-by: Jan Beulich <jbeulich@suse.com>