From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWXpG-0001HS-GW for qemu-devel@nongnu.org; Fri, 02 Dec 2011 13:27:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RWXpF-0002GR-Kr for qemu-devel@nongnu.org; Fri, 02 Dec 2011 13:27:10 -0500 Received: from va3ehsobe001.messaging.microsoft.com ([216.32.180.11]:34419 helo=VA3EHSOBE008.bigfish.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWXpF-0002G6-EJ for qemu-devel@nongnu.org; Fri, 02 Dec 2011 13:27:09 -0500 Message-ID: <4ED91876.2030408@freescale.com> Date: Fri, 2 Dec 2011 12:27:02 -0600 From: Scott Wood MIME-Version: 1.0 References: <20111103195452.21259.93021.stgit@bling.home> <4ED43AD9.5090509@au1.ibm.com> <4ED43CFE.8040009@au1.ibm.com> <1322538856.19120.126.camel@bling.home> <1322594768.19120.194.camel@bling.home> <1322610273.19120.209.camel@bling.home> <1322672293.19120.232.camel@bling.home> <1322774717.26545.118.camel@bling.home> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH] vfio: VFIO Driver core framework List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bhushan Bharat-R65777 Cc: "chrisw@sous-sol.org" , "agraf@suse.de" , Alexey Kardashevskiy , "kvm@vger.kernel.org" , "pmac@au1.ibm.com" , "joerg.roedel@amd.com" , Stuart Yoder , "qemu-devel@nongnu.org" , "iommu@lists.linux-foundation.org" , "konrad.wilk@oracle.com" , "aafabbri@cisco.com" , Yoder Stuart-B08248 , Alex Williamson , "avi@redhat.com" , "linux-pci@vger.kernel.org" , "dwg@au1.ibm.com" , Wood Scott-B07421 , "benve@cisco.com" On 12/02/2011 12:11 PM, Bhushan Bharat-R65777 wrote: > How do we determine whether guest is ready or not? There can be multiple device get ready at different time. The guest makes a hypercall with a device handle -- at least that's how we do it in Topaz. > Further if guest have given the device to it user level process or its guest. Should not there be some mechanism for a guest to enable/disable on per device or group? Yes, the same mechanism can be used for that -- though in that case we'll also want the ability for the guest to be able to control another layer of mapping (which will get quite tricky with PAMU's limitations). This isn't really VFIO's concern, though (unless you're talking about the VFIO implementation in the guest). -Scott