patch series introduces support for a user-creatable SMMUv3 device
(-device arm-smmuv3) in QEMU.
Tested-by: Nathan Chen
I re-ran the test from v3 [0] and am able to create 16 SMMUv3 devices in
a qemu VM with emulated devices properly associated with the guest SMMUs
in guest sysfs - verified
On 6/4/2025 7:34 PM, Donald Dutile wrote:
On 6/4/25 10:02 PM, Nathan Chen wrote:
On 6/2/2025 8:41 AM, Shameer Kolothum wrote:
This patch series introduces support for a user-creatable SMMUv3 device
(-device arm-smmuv3) in QEMU.
Tested-by: Nathan Chen
I am able to create 16 SMMUv3
On 6/2/2025 8:41 AM, Shameer Kolothum wrote:
This patch series introduces support for a user-creatable SMMUv3 device
(-device arm-smmuv3) in QEMU.
Tested-by: Nathan Chen
I am able to create 16 SMMUv3 devices in a qemu VM with emulated devices
properly associated with the guest SMMUs in
On 1/31/2025 8:08 AM, Eric Auger wrote:
And Qemu does some checking to make sure that the device is indeed
associated
with the specified phys-smmuv3. This can be done going through the
sysfs path checking
which is what I guess libvirt is currently doing to populate the
topology.
So basi
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
conf
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
conf
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
Hi Shameer,
Could you share the branch/version of the boot firmware file
"QEMU_EFI.fd" from your example, and where you retrieved it from? I've
been encountering PCI host bridge resource conflicts whenever assigning
more than one passthrough device to a multi-vSMMU VM, booting with the
boot f
> >> Also as a heads up, I've added support for auto-inserting PCIe switch
> >> between the PXB and GPUs in libvirt to attach multiple devices to a
> SMMU
> >> node per libvirt's documentation - "If you intend to plug multiple
> >> devices into a pcie-expander-bus, you must connect a
> >> pci
>> Also as a heads up, I've added support for auto-inserting PCIe switch
>> between the PXB and GPUs in libvirt to attach multiple devices to a SMMU
>> node per libvirt's documentation - "If you intend to plug multiple
>> devices into a pcie-expander-bus, you must connect a
>> pcie-switch-upstream
Hi Shameer,
> Attempt to add the HNS VF to a different SMMUv3 will result in,
>
> -device vfio-pci,host=:7d:02.2,bus=pcie.port3,iommufd=iommufd0:
Unable to attach viommu
> -device vfio-pci,host=:7d:02.2,bus=pcie.port3,iommufd=iommufd0:
vfio :7d:02.2:
>Failed to set iommu_device
11 matches
Mail list logo
