On Fri, Jun 04, 2021 at 09:30:54AM -0300, Jason Gunthorpe wrote: > On Fri, Jun 04, 2021 at 12:44:28PM +0200, Enrico Weigelt, metux IT consult wrote: > > On 02.06.21 19:24, Jason Gunthorpe wrote: > > > > Hi, > > > > >> If I understand this correctly, /dev/ioasid is a kind of "common > > supplier" > > >> to other APIs / devices. Why can't the fd be acquired by the > > >> consumer APIs (eg. kvm, vfio, etc) ? > > > > > > /dev/ioasid would be similar to /dev/vfio, and everything already > > > deals with exposing /dev/vfio and /dev/vfio/N together > > > > > > I don't see it as a problem, just more work. > > > > One of the problems I'm seeing is in container environments: when > > passing in an vfio device, we now also need to pass in /dev/ioasid, > > thus increasing the complexity in container setup (or orchestration). > > Containers already needed to do this today. Container orchestration is > hard. Right to use VFIO a container already needs both /dev/vfio and one or more /dev/vfio/NNN group devices. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
