> -----Original Message----- > From: Mario Smarduch [mailto:mario.smard...@huawei.com] > Sent: Thursday, July 04, 2013 9:45 AM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; Wood Scott-B07421; kvm@vger.kernel.org > list; Bhushan Bharat-R65777; > kvm-...@vger.kernel.org; virtualizat...@lists.linux-foundation.org; Sethi > Varun-B16395; > kvm...@lists.cs.columbia.edu > Subject: Re: RFC: vfio interface for platform devices (v2) > > > I'm having trouble understanding how this works where > the Guest Device Model != Host. How do you inform the guest > where the device is mapped in its physical address space, > and handle GPA faults?
The vfio mechanisms just expose hardware to user space and the user space app may or may not QEMU. So there may be no 'guest' at all. The intent of this RFC is to provide enough info to user space so an application can use the device, or in the case of QEMU expose the device to a VM. Platform devices are typically exposed via the device tree and that is how I envision them being presented to a guest. Are there real cases you see where guest device model != host? I don't envision ever presenting a platform device as a PCI device or vise versa. Stuart -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
