| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4BB4C591.8000102@redhat.com> Date: Thu, 01 Apr 2010 19:10:57 +0300 From: Avi Kivity <avi@...hat.com> To: Tom Lyon <pugs@...n-about.com> CC: kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/1] uio_pci_generic: extensions to allow access for non-privileged processes On 04/01/2010 07:06 PM, Tom Lyon wrote: > On Thursday 01 April 2010 08:54:14 am Avi Kivity wrote: > >> On 04/01/2010 06:39 PM, Tom Lyon wrote: >> >>>>> - support for MSI and MSI-X interrupts (the intel 82599 VFs support >>>>> only MSI-X) >>>>> >>>> How does a userspace program receive those interrupts? >>>> >>> Same as other UIO drivers - by read()ing an event counter. >>> >> IIRC the usual event counter is /dev/uioX, what's your event counter now? >> > Exact same mechanism. > But there are multiple msi-x interrupts, how do you know which one triggered? >> kvm really wants the event counter to be an eventfd, that allows hooking >> it directly to kvm (which can inject an interrupt on an eventfd_signal), >> can you adapt your patch to do this? >> > My patch does not currently go anywhere near the read/fd logic of /dev/uioX. > I think a separate patch would be appropriate. > Sure. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists