RE: [RFC PATCH v2 04/20] hw/arm/virt: Add support for smmuv3-accel

[Shameerali Kolothum Thodi via <qemu-arm@nongnu.org>]

> -----Original Message-----
> From: Donald Dutile <ddutile@redhat.com>
> Sent: Tuesday, March 18, 2025 10:50 PM
> To: Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>; qemu-arm@nongnu.org;
> qemu-devel@nongnu.org
> Cc: eric.auger@redhat.com; peter.maydell@linaro.org; jgg@nvidia.com;
> nicolinc@nvidia.com; berrange@redhat.com; nathanc@nvidia.com;
> mochs@nvidia.com; smostafa@google.com; Linuxarm
> <linuxarm@huawei.com>; Wangzhou (B) <wangzhou1@hisilicon.com>;
> jiangkunkun <jiangkunkun@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>; zhangfei.gao@linaro.org
> Subject: Re: [RFC PATCH v2 04/20] hw/arm/virt: Add support for smmuv3-
> accel
> 
> 
> Doesn't this commit become moot, if accel becomes an smmuv3 option vs
> separate device object altogether, dynamically added if a pdev is attached
> to a host SMMUv3 that has accel feature(s)?
> 
> Blocking w/virtio-iommu falls under the same situation mentioned in 03/20
> wrt mixing emulated & physical devices on the same smmuv3.

Yes, this patch might change once we move to "-device smmuv3, accel=on" version.

Thanks,
Shameer