> -----Original Message----- > From: Donald Dutile <ddut...@redhat.com> > Sent: Tuesday, March 18, 2025 10:50 PM > To: Shameerali Kolothum Thodi > <shameerali.kolothum.th...@huawei.com>; qemu-...@nongnu.org; > qemu-devel@nongnu.org > Cc: eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com; > nicol...@nvidia.com; berra...@redhat.com; nath...@nvidia.com; > mo...@nvidia.com; smost...@google.com; Linuxarm > <linux...@huawei.com>; Wangzhou (B) <wangzh...@hisilicon.com>; > jiangkunkun <jiangkun...@huawei.com>; Jonathan Cameron > <jonathan.came...@huawei.com>; zhangfei....@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
