Re: [Xen-devel] [iGVT-g] XenGT GPU virtualization

["Wang, Hongbo" <hongbo.wang@xxxxxxxxx>]

Intel XenGT has another maillist " igvt-g@xxxxxxxxxxxx" to discuss Intel GPU
virtualization questions, including XenGT and KVMGT. Feel free to subscribe.

Right now, we have two version GVT-g, "old architecture" vs "new
architecture for upstream"
Old architecture:
  - The codes are maintained off-tree, support both XenGT and KVMGT.
  - Our latest code is 2016Q3 version in Oct'16, 2016Q4 version is coming
   soon due to some open bugs.
  - 2016Q3 release blog:
   
https://01.org/igvt-g/blogs/wangbo85/2016/intel-gvt-g-iso-public-release-q32016 
  - Repo  Kernel: https://github.com/01org/igvtg-kernel 
         Xen: https://github.com/01org/igvtg-xen 
         QEMU: https://github.com/01org/igvtg-qemu 


New architecture for upstream:
  - KVMGT version with new VFIO interface have been upstreamed into
   kernel 4.10. You can see the code from kernel 4.10, or from our own 
   GVT-g repo which hosts latest code and bug fixing.
  - Repo Kernel:   https://github.com/01org/gvt-linux.git 
        QEMU:  git://git.qemu.org/qemu.git 
  - XenGT code upstream is ongoing, not upstreamed. So you can't see
   those code yet. We already have a workable XenGT version for upstream,
   may share the code after interface polishing.

More details about two versions, please refer to below introduction blog:
https://01.org/igvt-g/blogs/wangbo85/2017/gvt-g-upstream-status-update-were-transition-phase
 


Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@xxxxxxxxx

> -----Original Message-----
> From: iGVT-g [mailto:igvt-g-bounces@xxxxxxxxxxxx] On Behalf Of Haozhong
> Zhang
> Sent: Friday, February 24, 2017 9:43 AM
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx; 'bharat gohil' <ghl.bhrt@xxxxxxxxx>;
> igvt-g@xxxxxxxxxxxx
> Subject: Re: [iGVT-g] [Xen-devel] XenGT GPU virtualization
> 
> Cc'ed to the mailing list of Intel graphic virtualization
> 
> [Sorry for the spam. The last cc failed as I didn't subscribe to
> igvt-g@xxxxxxxxxxxx]
> 
> On 02/23/17 12:36 +0000, Paul Durrant wrote:
> > Hi,
> >
> >   I’m not actually sure where the latest public release of the xengt code
> is. Perhaps someone from Intel can comment?
> >
> >   Otherwise, if you grab the source ISOs from xenserver.org you can look
> in the SRPM for xengt. The xengt kernel module is responsible for auditing
> the servicing the GPU commands from guests.
> >
> >   Cheers,
> >
> >   Paul
> >
> >
> > From: bharat gohil [mailto:ghl.bhrt@xxxxxxxxx]
> > Sent: 23 February 2017 12:30
> > To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> > Cc: Anshul Makkar <anshul.makkar@xxxxxxxxxx>;
> xen-devel@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] XenGT GPU virtualization
> >
> > Thanks paul and anshul
> > Can you guys point out source code which is audit the GPU command?
> >
> > Thanks
> > Bharat
> >
> > On Mon, Feb 20, 2017 at 9:01 PM, Paul Durrant
> <Paul.Durrant@xxxxxxxxxx<mailto:Paul.Durrant@xxxxxxxxxx>> wrote:
> > No, that’s not correct. The GPU commands are whitelisted and only the
> commands that can be audited are handled.
> >
> >   Paul
> >
> > From: Xen-devel
> [mailto:xen-devel-bounces@xxxxxxxxxxxxx<mailto:xen-devel-bounces@lists.x
> en.org>] On Behalf Of anshul makkar
> > Sent: 20 February 2017 15:16
> > To: bharat gohil <ghl.bhrt@xxxxxxxxx<mailto:ghl.bhrt@xxxxxxxxx>>;
> xen-devel@xxxxxxxxxxxxxxxxxxxx<mailto:xen-devel@xxxxxxxxxxxxxxxxxxxx>
> > Subject: Re: [Xen-devel] XenGT GPU virtualization
> >
> >
> >
> >
> > On 18/01/17 13:21, bharat gohil wrote:
> > Hello
> >
> > I am new to GPU and GPU virtualization and found that xen support intel
> GPU virtualization using XenGT.
> > I want to know,
> > 1) What are the critical GPU command pass from xen to Dom0?
> > 2) How the Dom0 mediator or xen validate the GPU command which is
> passed from domU GPU driver?
> > 3) If one of the domU guest send bad(malicious) command to GPU which
> led GPU to bad state. Can Dom0 mediator or xen prevents this kind of
> scenario?
> > As far as I know, there is know mediation to check for the commands. Xen
> does audit the target address space, but not GPU commands.
> >
> > --
> > Regards,
> > Bharat Gohil
> >
> >
> >
> >
> > _______________________________________________
> >
> > Xen-devel mailing list
> >
> > Xen-devel@xxxxxxxxxxxxx<mailto:Xen-devel@xxxxxxxxxxxxx>
> >
> > https://lists.xen.org/xen-devel
> >
> >
> >
> >
> > --
> > Regards,
> > Bharat Gohil
> > Sr.Software Engineer
> > bharat.gohil@xxxxxxxxxx<mailto:bharat.gohil@xxxxxxxxxx>
> > +919427054633
> 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx
> > https://lists.xen.org/xen-devel
> 
> _______________________________________________
> iGVT-g mailing list
> iGVT-g@xxxxxxxxxxxx
> https://lists.01.org/mailman/listinfo/igvt-g
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel