[why are you top-posting?] On Mon, Oct 05, 2015 at 11:42:38AM +0200, Baptiste Reynal wrote: > In this patch series we want to wrap an already available kernel > interface to expose a device property to userspace,
which 'already available kernel interface' is that exactly? > in order to keep > the code lighter on the userspace. We need those properties in VFIO as I'm not sure I agree with your 'need those properties in VFIO' statement here, can you elaborate? > VFIO grants the possibility to develop userspace drivers. > > The sysfs doesn't seems to be ready for this kind of usage. We can > only find raw data that require heavy parsing. Here we retrieve > directly usable data and it can be extended later according to new > needs (as it is already done with ACPI). Why couldn't you expose this kind of data through sysfs instead of VFIO and independently of VFIO? Would that be more wrong/difficult/whatever? > > This interface has been developed for VFIO and is currently bound to > it, though there is no special dependencies with it. We could make it > more generic, but I can only think of VFIO to use it. Thanks, -Christoffer _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
