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
| ||
|
Date: Fri, 20 Nov 2015 10:58:25 +0800 From: Jike Song <jike.song@...el.com> To: Alex Williamson <alex.williamson@...hat.com> CC: Stefano Stabellini <stefano.stabellini@...citrix.com>, "Tian, Kevin" <kevin.tian@...el.com>, "xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>, "igvt-g@...1.01.org" <igvt-g@...1.01.org>, "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "White, Michael L" <michael.l.white@...el.com>, "Dong, Eddie" <eddie.dong@...el.com>, "Li, Susie" <susie.li@...el.com>, "Cowperthwaite, David J" <david.j.cowperthwaite@...el.com>, "Reddy, Raghuveer" <raghuveer.reddy@...el.com>, "Zhu, Libo" <libo.zhu@...el.com>, "Zhou, Chao" <chao.zhou@...el.com>, "Wang, Hongbo" <hongbo.wang@...el.com>, "Lv, Zhiyuan" <zhiyuan.lv@...el.com>, qemu-devel <qemu-devel@...gnu.org>, Paolo Bonzini <pbonzini@...hat.com>, Gerd Hoffmann <kraxel@...hat.com> Subject: Re: [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel On 11/19/2015 11:52 PM, Alex Williamson wrote: > On Thu, 2015-11-19 at 15:32 +0000, Stefano Stabellini wrote: >> On Thu, 19 Nov 2015, Jike Song wrote: >>> Hi Alex, thanks for the discussion. >>> >>> In addition to Kevin's replies, I have a high-level question: can VFIO >>> be used by QEMU for both KVM and Xen? >> >> No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU >> is owned by Xen. > > Right, but in this case we're talking about device MMUs, which are owned > by the device driver which I think is running in dom0, right? This > proposal doesn't require support of the system IOMMU, the dom0 driver > maps IOVA translations just as it would for itself. We're largely > proposing use of the VFIO API to provide a common interface to expose a > PCI(e) device to QEMU, but what happens in the vGPU vendor device and > IOMMU backends is specific to the device and perhaps even specific to > the hypervisor. Thanks, Let me conclude this, and please correct me in case of any misread: the vGPU interface between kernel and QEMU will be through VFIO, with a new VFIO backend (instead of the existing type1), for both KVMGT and XenGT? > > Alex > -- Thanks, Jike -- 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