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:46:54 +0800 From: Jike Song <jike.song@...el.com> To: Paolo Bonzini <pbonzini@...hat.com> CC: Gerd Hoffmann <kraxel@...hat.com>, "Tian, Kevin" <kevin.tian@...el.com>, Alex Williamson <alex.williamson@...hat.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> Subject: Re: [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel On 11/19/2015 07:09 PM, Paolo Bonzini wrote: > On 19/11/2015 09:40, Gerd Hoffmann wrote: >>>> But this code should be >>>> minor to be maintained in libvirt. >> As far I know libvirt only needs to discover those devices. If they >> look like sr/iov devices in sysfs this might work without any changes to >> libvirt. > > I don't think they will look like SR/IOV devices. > > The interface may look a little like the sysfs interface that GVT-g is > already using. However, it should at least be extended to support > multiple vGPUs in a single VM. This might not be possible for Intel > integrated graphics, but it should definitely be possible for discrete > graphics cards. Didn't hear about multiple vGPUs for a single VM before. Yes If we expect same vGPU interfaces for different vendors, abstraction and vendor specific stuff should be implemented. > Another nit is that the VM id should probably be replaced by a UUID > (because it's too easy to stumble on an existing VM id), assuming a VM > id is needed at all. For the last assumption, yes, a VM id is not necessary for gvt-g, it's only a temporary implementation. As long as libvirt is used, UUID should be enough for gvt-g. However, UUID is not mandatory? What should we do if user don't specify an UUID in QEMU cmdline? > > Paolo > -- 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