From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH corrected RFC] uio: add generic driver for PCI 2.3 devices Date: Sun, 12 Jul 2009 09:17:01 +0300 Message-ID: <4A597FDD.7040205@redhat.com> References: <20090709114834.GB26479@redhat.com> <4A5604B3.2090508@codemonkey.ws> <20090710022229.GF30379@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , "Michael S. Tsirkin" , kvm@vger.kernel.org To: Chris Wright Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57759 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbZGLGQ7 (ORCPT ); Sun, 12 Jul 2009 02:16:59 -0400 In-Reply-To: <20090710022229.GF30379@sequoia.sous-sol.org> Sender: kvm-owner@vger.kernel.org List-ID: On 07/10/2009 05:22 AM, Chris Wright wrote: >> I know it's not strictly needed for PCI pass through, but it would be >> useful to register the IO regions via UIO. The userspace implementation >> would then use UIO strictly instead of poking the sysfs pci info >> directly. I think that ends up being cleaner. >> > > I don't see what the advantage is? > Have a single fd represent the assigned device, so security can be concentrated at that point. Some privileged server can then hand out the fd to qemu. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.