Re: kvm PCI assignment VFIO ramblings

2011-08-23 Thread aafabbri
On 8/23/11 4:04 AM, Joerg Roedel joerg.roe...@amd.com wrote: On Mon, Aug 22, 2011 at 08:52:18PM -0400, aafabbri wrote: You have to enforce group/iommu domain assignment whether you have the existing uiommu API, or if you change it to your proposed ioctl(inherit_iommu) API. The only

Re: kvm PCI assignment VFIO ramblings

2011-08-22 Thread aafabbri
On 8/20/11 9:51 AM, Alex Williamson alex.william...@redhat.com wrote: We had an extremely productive VFIO BoF on Monday. Here's my attempt to capture the plan that I think we agreed to: We need to address both the description and enforcement of device groups. Groups are formed any time

Re: kvm PCI assignment VFIO ramblings

2011-08-22 Thread aafabbri
On 8/22/11 1:49 PM, Benjamin Herrenschmidt b...@kernel.crashing.org wrote: On Mon, 2011-08-22 at 13:29 -0700, aafabbri wrote: Each device fd would then support a similar set of ioctls and mapping (mmio/pio/config) interface as current vfio, except for the obvious domain and dma ioctls

Re: kvm PCI assignment VFIO ramblings

2011-08-22 Thread aafabbri
On 8/22/11 2:49 PM, Benjamin Herrenschmidt b...@kernel.crashing.org wrote: I wouldn't use uiommu for that. Any particular reason besides saving a file descriptor? We use it today, and it seems like a cleaner API than what you propose changing it to. Well for one, we are back to