Re: [RFC PATCH 0/5] VFIO-NG group/device/iommu framework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01.09.2011, at 21:50, Alex Williamson wrote:

> Trying to move beyond talking about how VFIO should work to
> re-writing the code.  This is pre-alpha, known broken, will
> probably crash your system but it illustrates some of how
> I see groups, devices, and iommus interacting.  This is just
> the framework, no code to actually support user space drivers
> or device assignment yet.
> 
> The iommu portions are still using the "FIXME" PCI specific
> hooks.  Once Joerg gets some buy-in on his bus specific iommu
> patches, we can move to that.
> 
> The group management is more complicated than I'd like and
> you can get groups into a bad state by killing the test program
> with devices/iommus open.  The locking is overly simplistic.
> But, it's a start.  Please make constructive comments and
> suggestions.  Patches based on v3.0.  Thanks,

Looks pretty reasonable to me so far, but I guess we only know for sure once we have non-PCI implemented and working with this scheme as well.
Btw I couldn't find the PCI BAR regions mmaps and general config space exposure. Where has that gone?


Alex

--
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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux