Skip to contentSkip to conversation

Different type iommus integrated in a SoC

DISCUSSION [email protected] 4 participants 5 messages May 27, 2021 – Jun 4, 2021 Arm Rockchip

lore
Share & tools
lore
#0 lore raw

Hi all,

I have a SoC integrate with two different types of iommus, one is ARM SMMU, serves the PCIe/SATA/USB, the others are vendor specific iommus, serves display device and multimedia device.

In the current linux kernel, the iommu framework seems only support one type iommu at runtime, if enable both types iommu, only one type can work. Is there any way to support this kind of SoC?

Simon

_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu

#1 lore raw
Quoted 7 lines · On 2021-05-27 03:37, [email protected] wrote:

Hi all,

I have a SoC integrate with two different types of iommus, one is ARM SMMU, serves the PCIe/SATA/USB, the others are vendor specific iommus, serves display device and multimedia device.

In the current linux kernel, the iommu framework seems only support one type iommu at runtime, if enable both types iommu, only one type can work. Is there any way to support this kind of SoC?

Hooray! I've been forecasting this for years, but the cases we regularly hit with internal FPGA prototyping (nor the secret unused MMU-400 I found on RK3288) have never really been a strong enough argument to stand behind.

Based on what I remember from looking into this a few years ago, converting *most* of the API to per-device ops (now via dev->iommu) is trivial; the main challenge will be getting the per-device data bootstrapped in iommu_probe_device(), which would probably need to rely on the fwspec and/or list of registered IOMMU instances.

The other notable thing which will need to change is the domain allocation interface, but in practice I think everyone who calls iommu_domain_alloc() today is in fact doing so for a specific device, so I don't think it's as big a problem as it might first appear.

Robin.
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu

#2 lore raw
Quoted 21 lines · Robin Murphy
Quoted 7 lines · On 2021-05-27 03:37, [email protected] wrote:

Hi all,

I have a SoC integrate with two different types of iommus, one is ARM SMMU, serves the PCIe/SATA/USB, the others are vendor specific iommus, serves display device and multimedia device.

In the current linux kernel, the iommu framework seems only support one type iommu at runtime, if enable both types iommu, only one type can work. Is there any way to support this kind of SoC?

Hooray! I've been forecasting this for years, but the cases we regularly hit with internal FPGA prototyping (nor the secret unused MMU-400 I found on RK3288) have never really been a strong enough argument to stand behind.

Based on what I remember from looking into this a few years ago, converting *most* of the API to per-device ops (now via dev->iommu) is trivial; the main challenge will be getting the per-device data bootstrapped in iommu_probe_device(), which would probably need to rely on the fwspec and/or list of registered IOMMU instances.

Quoted 7 lines

The other notable thing which will need to change is the domain allocation interface, but in practice I think everyone who calls iommu_domain_alloc() today is in fact doing so for a specific device, so I don't think it's as big a problem as it might first appear.

Robin.

Good Morning Robin,

I think the Tegra group would also be interested in this work. AFAIK they have the smmu and the tegra gart and have been trying to figure out the runtime handover from the bootloader to the kernel without smashing everything and starting over.

Thanks,
Peter Geis

_______________________________________________
Linux-rockchip mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-rockchip

#3 lore raw
Quoted 30 lines · Peter Geis
Quoted 21 lines · Robin Murphy
Quoted 7 lines · On 2021-05-27 03:37, [email protected] wrote:

Hi all,

I have a SoC integrate with two different types of iommus, one is ARM SMMU, serves the PCIe/SATA/USB, the others are vendor specific iommus, serves display device and multimedia device.

In the current linux kernel, the iommu framework seems only support one type iommu at runtime, if enable both types iommu, only one type can work. Is there any way to support this kind of SoC?

Hooray! I've been forecasting this for years, but the cases we regularly hit with internal FPGA prototyping (nor the secret unused MMU-400 I found on RK3288) have never really been a strong enough argument to stand behind.

Based on what I remember from looking into this a few years ago, converting *most* of the API to per-device ops (now via dev->iommu) is trivial; the main challenge will be getting the per-device data bootstrapped in iommu_probe_device(), which would probably need to rely on the fwspec and/or list of registered IOMMU instances.

Quoted 7 lines

The other notable thing which will need to change is the domain allocation interface, but in practice I think everyone who calls iommu_domain_alloc() today is in fact doing so for a specific device, so I don't think it's as big a problem as it might first appear.

Robin.

Quoted 6 lines

Good Morning Robin,

I think the Tegra group would also be interested in this work. AFAIK they have the smmu and the tegra gart and have been trying to figure out the runtime handover from the bootloader to the kernel without smashing everything and starting over.

No, handoff of live DMA from the bootlader is an entirely unrelated issue, and there are already several patchsets in flight to address various parts of that. My understanding of Tegras is that they *either* use tegra-gart, tegra-smmu, or arm-smmu depending on the SoC generation, but they aren't mixed within any single SoC.

Robin.
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu

#4 lore raw
In reply to Robin Murphy
Quoted 10 lines · Robin Murphy

Hooray! I've been forecasting this for years, but the cases we regularly hit with internal FPGA prototyping (nor the secret unused MMU-400 I found on RK3288) have never really been a strong enough argument to stand behind.

Based on what I remember from looking into this a few years ago, converting *most* of the API to per-device ops (now via dev->iommu) is trivial; the main challenge will be getting the per-device data bootstrapped in iommu_probe_device(), which would probably need to rely on the fwspec and/or list of registered IOMMU instances.

Quoted 4 lines

The other notable thing which will need to change is the domain allocation interface, but in practice I think everyone who calls iommu_domain_alloc() today is in fact doing so for a specific device, so I don't think it's as big a problem as it might first appear.

Yeah, I think for that we have to give up on the promise that a domain can be assigned to _any_ device. But this promise doesn't even hold true now when there are several IOMMU of the same type but with different feature sets in a system.

So I happily review patches enabling the Multi-IOMMU SOCs :)

Regards,

Joerg
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu