xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Wang, Hongbo" <hongbo.wang@intel.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"igvt-g@lists.01.org" <igvt-g@ml01.01.org>,
	Paul Durrant <Paul.Durrant@citrix.com>,
	'bharat gohil' <ghl.bhrt@gmail.com>,
	"Zhang, Haozhong" <haozhong.zhang@intel.com>
Subject: Re: [iGVT-g]  XenGT GPU virtualization
Date: Tue, 28 Feb 2017 10:07:18 -0500	[thread overview]
Message-ID: <20170228150718.GJ25998@char.us.oracle.com> (raw)
In-Reply-To: <2A893DE636717B4D96C6AAB5599D2CF91A9EA479@SHSMSX103.ccr.corp.intel.com>

On Fri, Feb 24, 2017 at 02:25:27AM +0000, Wang, Hongbo wrote:
> Intel XenGT has another maillist " igvt-g@lists.01.org" 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.

Could you expand on that please? I thought the ioreq multiple
servers were the big dependency but it sounds like there is more work?

What is involved here?


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-02-28 15:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 13:21 XenGT GPU virtualization bharat gohil
2017-01-31 21:29 ` Konrad Rzeszutek Wilk
2017-02-20 15:16 ` anshul makkar
2017-02-20 15:31   ` Paul Durrant
2017-02-23 12:29     ` bharat gohil
2017-02-23 12:36       ` Paul Durrant
2017-02-24  1:24         ` Haozhong Zhang
2017-02-24  1:42         ` Haozhong Zhang
2017-02-24  2:25           ` [iGVT-g] " Wang, Hongbo
2017-02-24  6:58             ` bharat gohil
2017-02-28 15:07             ` Konrad Rzeszutek Wilk [this message]
2017-03-01 14:36               ` Zhiyuan Lv
2017-03-01 19:50                 ` Konrad Rzeszutek Wilk
2017-02-24  1:23 ` Haozhong Zhang
2017-02-24  1:38 ` Haozhong Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170228150718.GJ25998@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=ghl.bhrt@gmail.com \
    --cc=haozhong.zhang@intel.com \
    --cc=hongbo.wang@intel.com \
    --cc=igvt-g@ml01.01.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).