On Sun, Nov 28, 2021 at 07:15:09PM -0400, Jason Gunthorpe wrote:
> On Sun, Nov 28, 2021 at 09:10:14AM +0100, Greg Kroah-Hartman wrote:
> > On Sun, Nov 28, 2021 at 10:50:38AM +0800, Lu Baolu wrote:
> > > Multiple platform devices may be placed in the same IOMMU group because
> > > they cannot be isolated from each other. These devices must either be
> > > entirely under kernel control or userspace control, never a mixture. This
> > > checks and sets DMA ownership during driver binding, and release the
> > > ownership during driver unbinding.
> > >
> > > Driver may set a new flag (suppress_auto_claim_dma_owner) to disable auto
> > > claiming DMA_OWNER_DMA_API ownership in the binding process. For instance,
> > > the userspace framework drivers (vfio etc.) which need to manually claim
> > > DMA_OWNER_PRIVATE_DOMAIN_USER when assigning a device to userspace.
> >
> > Why would any vfio driver be a platform driver?
>
> Why not? VFIO implements drivers for most physical device types
> these days. Why wouldn't platform be included?
Because "platform" is not a real device type. It's a catch-all for
devices that are only described by firmware, so why would you have a
virtual device for that? Why would that be needed?
> > > diff --git a/include/linux/platform_device.h b/include/linux/platform_device.h
> > > index 7c96f169d274..779bcf2a851c 100644
> > > +++ b/include/linux/platform_device.h
> > > @@ -210,6 +210,7 @@ struct platform_driver {
> > > struct device_driver driver;
> > > const struct platform_device_id *id_table;
> > > bool prevent_deferred_probe;
> > > + bool suppress_auto_claim_dma_owner;
> >
> > What platform driver needs this change?
>
> It is in patch 12:
>
> --- a/drivers/vfio/platform/vfio_platform.c
> +++ b/drivers/vfio/platform/vfio_platform.c
Ok, nevermind, you do have a virtual platform device, which personally,
I find crazy as why would firmware export a "virtual device"?
> @@ -76,6 +76,7 @@ static struct platform_driver vfio_platform_driver = {
> .driver = {
> .name = "vfio-platform",
> },
> + .suppress_auto_claim_dma_owner = true,
> };
>
> Which is how VFIO provides support to DPDK for some Ethernet
> controllers embedded in a few ARM SOCs.
Ick. Where does the DT file for these devices live that describe a
"virtual device" to match with this driver?
> It is also used in patch 17 in five tegra platform_drivers to make
> their sharing of an iommu group between possibly related
> platform_driver's safer.
Safer how?
> > > USE_PLATFORM_PM_SLEEP_OPS
> > > @@ -1478,7 +1505,8 @@ struct bus_type platform_bus_type = {
> > > .probe = platform_probe,
> > > .remove = platform_remove,
> > > .shutdown = platform_shutdown,
> > > - .dma_configure = platform_dma_configure,
> > > + .dma_configure = _platform_dma_configure,
> >
> > What happened to the original platform_dma_configure() function?
>
> It is still called. The issue here is that platform_dma_configure has
> nothing to do with platform and is being re-used by AMBA.
Ick, why? AMBA needs to be a real bus type and use their own functions
if needed. There is nothing here that makes this obvious that someone
else is using those functions and that the platform bus should only be
using these "new" functions.
> Probably the resolution to both remarks is to rename
> platform_dma_configure to something sensible (firwmare dma configure
> maybe?) and use it in all places that do the of & acpi stuff -
> pci/amba/platform at least.
That would be better than what is being proposed here.
thanks,
greg k-h
