From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominic Eschweiler Subject: Re: [PATCH] uio_pci_generic does not export memory resources Date: Fri, 08 Jun 2012 16:47:47 +0200 Message-ID: <1339166867.3870.29.camel@blech> References: <1339156616.3870.9.camel@blech> <20120608130351.GB1964@redhat.com> <4FD1FB49.3020905@siemens.com> <1339165009.26976.60.camel@ul30vt> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jan Kiszka , "Michael S. Tsirkin" , "Hans J. Koch" , Greg Kroah-Hartman , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Alex Williamson Return-path: In-Reply-To: <1339165009.26976.60.camel@ul30vt> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Am Freitag, den 08.06.2012, 08:16 -0600 schrieb Alex Williamson: > Yes, thanks Jan. This is exactly what VFIO does. VFIO provides > secure config space access, resource access, DMA mapping services, an= d > full interrupt support to userspace. =20 I know about VFIO, but we need some support for that stuff relatively soon. That's the reason why I'm currently working on it to make UIO DMA capable. My extensions probably do not play well with IOMMUs and they therefore won't make it to mainline anyhow (i learned that today ;-). > I'm currently working to get this upstream, probably targeting 3.6 at > this point, and would love to have more users to help make that > happen. =20 Yes, you are faster than I'm able to ask. 3.6 is a good target and really would like to support that. > Please take a look at the vfio-3.4 branch in the tree above. See thi= s > tree for Qemu's usage of VFIO for device assignment ... OK, I take look at it and report back (off the list). Please write me a= n email if you need support. --=20 Gru=C3=9F Dominic =46rankfurt Institute for Advanced Studies (FIAS) Ruth-Moufang-Stra=C3=9Fe 1 D-60438 Frankfurt am Main Germany Phone: +49 69 79844114