intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"Yuan, Hang" <hang.yuan@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [GIT PULL] more gvt-next for 4.16
Date: Tue, 5 Dec 2017 16:52:14 -0800	[thread overview]
Message-ID: <20171206005214.dsmgwyuhqueryaps@intel.com> (raw)
In-Reply-To: <20171205032629.vylemph57toipeax@zhen-hp.sh.intel.com>


Applied. Thanks,

I noticed the KBL patch and got curious... what about CFL and CNL?

Thanks,
Rodrigo.

On Tue, Dec 05, 2017 at 03:26:29AM +0000, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's more gvt-next updates for 4.16. Mostly for final VFIO mdev
> display dmabuf interface and gvt implementation which have been
> reviewed by VFIO maintainer and acked to push through gvt merge path.
> User space qemu support was sent as
> https://lists.nongnu.org/archive/html/qemu-devel/2017-10/msg02213.html,
> and tracked at
> https://www.kraxel.org/cgit/qemu/log/?h=work/intel-vgpu
> 
> Others include VFIO opregion support, scheduler optimization and
> preemption fix, etc.
> 
> thanks
> --
> The following changes since commit f2880e04f3a5419366926182fc97a3c2e4fd8f2a:
> 
>   drm/i915/gvt: Move request alloc to dispatch_workload path only (2017-11-16 11:51:55 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2017-12-05
> 
> for you to fetch changes up to 1603660b3342269c95fcafee1945790342a8c28e:
> 
>   drm/i915/gvt: set max priority for gvt context (2017-12-04 11:24:35 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-2017-12-05
> 
> - VFIO mdev display dmabuf interface and gvt support (Tina)
> - VFIO mdev opregion support/fixes (Tina/Xiong/Chris)
> - workload scheduling optimization (Changbin)
> - preemption fix and temporal workaround (Zhenyu)
> - and misc fixes after refactor (Chris)
> 
> ----------------------------------------------------------------
> Changbin Du (2):
>       drm/i915/gvt: Convert macro queue_workload to a function
>       drm/i915/gvt: Kick scheduler when new workload queued
> 
> Chris Wilson (2):
>       drm/i915/gvt: Cleanup unwanted public symbols
>       drm/i915/gvt: Fix out-of-bounds buffer write into opregion->signature[]
> 
> Tina Zhang (7):
>       drm/i915/gvt: Add opregion support
>       drm/i915/gvt: Add framebuffer decoder support
>       vfio: ABI for mdev display dma-buf operation
>       drm/i915/gvt: Dmabuf support for GVT-g
>       drm/i915/gvt: Handle orphan dmabuf_objs
>       drm/i915/gvt: Introduce KBL to dma-buf on Gvt-g
>       drm/i915/gvt: Free dmabuf_obj list in intel_vgpu_dmabuf_cleanup
> 
> Xiong Zhang (1):
>       drm/i915/gvt: Alloc and Init guest opregion at vgpu creation
> 
> Zhenyu Wang (2):
>       drm/i915/gvt: Don't mark vgpu context as inactive when preempted
>       drm/i915/gvt: set max priority for gvt context
> 
>  drivers/gpu/drm/i915/gvt/Makefile       |   3 +-
>  drivers/gpu/drm/i915/gvt/cfg_space.c    |   3 +-
>  drivers/gpu/drm/i915/gvt/display.c      |   2 +-
>  drivers/gpu/drm/i915/gvt/display.h      |   2 +
>  drivers/gpu/drm/i915/gvt/dmabuf.c       | 538 ++++++++++++++++++++++++++++++++
>  drivers/gpu/drm/i915/gvt/dmabuf.h       |  67 ++++
>  drivers/gpu/drm/i915/gvt/execlist.c     |   8 +-
>  drivers/gpu/drm/i915/gvt/fb_decoder.c   | 508 ++++++++++++++++++++++++++++++
>  drivers/gpu/drm/i915/gvt/fb_decoder.h   | 169 ++++++++++
>  drivers/gpu/drm/i915/gvt/gvt.c          |   2 +
>  drivers/gpu/drm/i915/gvt/gvt.h          |  17 +-
>  drivers/gpu/drm/i915/gvt/hypercall.h    |   3 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c        | 161 +++++++++-
>  drivers/gpu/drm/i915/gvt/mpt.h          |  45 +++
>  drivers/gpu/drm/i915/gvt/opregion.c     | 137 +++++---
>  drivers/gpu/drm/i915/gvt/sched_policy.c |   5 +
>  drivers/gpu/drm/i915/gvt/sched_policy.h |   2 +
>  drivers/gpu/drm/i915/gvt/scheduler.c    |  21 +-
>  drivers/gpu/drm/i915/gvt/scheduler.h    |   7 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c         |  17 +-
>  drivers/gpu/drm/i915/i915_gem_object.h  |   2 +
>  include/uapi/linux/vfio.h               |  62 ++++
>  22 files changed, 1709 insertions(+), 72 deletions(-)
>  create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.c
>  create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.h
>  create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.c
>  create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.h
> 
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-12-06  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  3:26 [GIT PULL] more gvt-next for 4.16 Zhenyu Wang
2017-12-06  0:52 ` Rodrigo Vivi [this message]

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=20171206005214.dsmgwyuhqueryaps@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=kraxel@redhat.com \
    --cc=kwankhede@nvidia.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@intel.com \
    /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).