On 05/31/2010 08:10 PM, Michael S. Tsirkin wrote:
On Mon, May 31, 2010 at 02:50:29PM +0300, Avi Kivity wrote:
On 05/30/2010 05:53 PM, Michael S. Tsirkin wrote:
So what I suggested is failing any kind of access until iommu
is assigned.
So, the kernel driver must be aware of the iommu. In which case it may
as well program it.
It's a kernel driver anyway. Point is that
the *device* driver is better off not programming iommu,
this way we do not need to reprogram it for each device.
The device driver is in userspace. It can't program the iommu. What
the patch proposes is that userspace tells vfio about the needed
mappings, and vfio programs the iommu.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
