Re: [PATCH 0/3] VFIO V4: VFIO driver: Non-privileged user level PCI drivers

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

 



On Wed, 22 Sep 2010 14:15:57 -0700
Tom Lyon <pugs@xxxxxxxxx> wrote:

> After a long summer break, it's tanned, it's rested, and it's ready to rumble!
> 
> In this version:	*** REBASE to 2.6.35 ***
> 
> There's new code using generic netlink messages which allows the kernel
> to notify the user level of weird events and allows the user level to 
> respond. This is currently used to handle device removal (whether software
> or hardware driven), PCI error events, and system suspend & hibernate.
> 
> The driver now supports devices which use multiple MSI interrupts, reflecting
> the actual number of interrupts allocated by the system to the user level.
> 
> PCI config accesses are now done through the pci_user_{read,write)_config
> routines from drivers/pci/access.c.
> 

I really don't like to encourage user level drivers (in fact I've
actively tried to kill them in our graphics stack), but I do understand
that they're convenient in many scenarios.

So assuming you can convince someone to apply the VFIO framework, I'm
ok with exporting the user level accessor functions (after all, we
export them to userland already via sysfs, so exporting them as GPL
symbols to another module is fine).

So you can add my Acked-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> to
the PCI parts, but don't take it as an endorsement of VFIO in
general! :) 

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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