> -----Original Message----- > From: Nicolin Chen <nicol...@nvidia.com> > Sent: Monday, March 17, 2025 8:19 PM > To: Jason Gunthorpe <j...@nvidia.com> > Cc: Eric Auger <eric.au...@redhat.com>; Shameerali Kolothum Thodi > <shameerali.kolothum.th...@huawei.com>; qemu-...@nongnu.org; > qemu-devel@nongnu.org; peter.mayd...@linaro.org; ddut...@redhat.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 03/20] hw/arm/smmuv3-accel: Add initial > infrastructure for smmuv3-accel device > > On Mon, Mar 17, 2025 at 04:24:53PM -0300, Jason Gunthorpe wrote: > > On Mon, Mar 17, 2025 at 12:10:19PM -0700, Nicolin Chen wrote: > > > Another question: how does an emulated device work with a > vSMMUv3? > > > I could imagine that all the accel steps would be bypassed since > > > !sdev->idev. Yet, the emulated iotlb should cache its translation > > > so we will need to flush the iotlb, which will increase complexity > > > as the TLBI command dispatching function will need to be aware what > > > ASID is for emulated device and what is for vfio device.. > > > > I think you should block it. We already expect different vSMMU's > > depending on the physical SMMU under the PCI device, it makes sense > > that a SW VFIO device would have it's own, non-accelerated, vSMMU > > model in the guest. > > Yea, I agree and it'd be cleaner for an implementation separating > them. > > In my mind, the general idea of "accel=on" is also to keep things > in a more efficient way: passthrough devices go to HW-accelerated > vSMMUs (separated PCIE buses), while emulated ones go to a vSMMU- > bypassed (PCIE0). > > Though I do see the point from QEMU prospective that user may want > to start a VM with HW-accelerated vSMMU for one passthrough device > using a simple setup without caring about the routing via command. For now we don't use iotlb for accel cases with emulated devices. So probably can document/warn the user about possible performance degradation if they attach such a device rather than blocking. Thanks, Shameer
RE: [RFC PATCH v2 03/20] hw/arm/smmuv3-accel: Add initial infrastructure for smmuv3-accel device
Shameerali Kolothum Thodi via Tue, 18 Mar 2025 23:05:12 -0700
- Re: [RFC PATCH v2 ... Donald Dutile
- Re: [RFC PATCH v2 ... Eric Auger
- RE: [RFC PATCH v2 ... Shameerali Kolothum Thodi via
- Re: [RFC PATCH v2 ... Eric Auger
- Re: [RFC PATCH v2 03/2... Eric Auger
- Re: [RFC PATCH v2 ... Donald Dutile
- Re: [RFC PATCH v2 ... Eric Auger
- Re: [RFC PATCH v2 03/20] hw/arm... Jason Gunthorpe
- Re: [RFC PATCH v2 03/20] hw... Nicolin Chen
- Re: [RFC PATCH v2 03/20] hw... Eric Auger
- RE: [RFC PATCH v2 03/20] hw/arm/smm... Shameerali Kolothum Thodi via
- Re: [RFC PATCH v2 03/20] hw/arm/smmuv3-... Donald Dutile
- Re: [RFC PATCH v2 03/20] hw/arm/smmuv3-accel... Eric Auger
- RE: [RFC PATCH v2 03/20] hw/arm/smmuv3-... Shameerali Kolothum Thodi via
- Re: [RFC PATCH v2 03/20] hw/arm/smm... Eric Auger
- Re: [RFC PATCH v2 03/20] hw/arm... Jason Gunthorpe
- Re: [RFC PATCH v2 03/20] hw... Eric Auger
- Re: [RFC PATCH v2 03/20] hw/arm/smmuv3-... Nicolin Chen
- Re: [RFC PATCH v2 03/20] hw/arm/smm... Eric Auger
- Re: [RFC PATCH v2 03/20] hw/arm... Nicolin Chen
- Re: [RFC PATCH v2 03/20] hw... Eric Auger