public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [GIT PULL] more GVT-g fixes for 4.11
Date: Mon, 27 Mar 2017 11:44:10 +0300	[thread overview]
Message-ID: <87zig785yd.fsf@intel.com> (raw)
In-Reply-To: <20170323091734.znjnbvkr6dnazziq@zhen-hp.sh.intel.com>

On Thu, 23 Mar 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> Here's updated gvt fixes for 4.11. Major ones are for KVM reference
> fix, guest gtt partial update fix for very big guest mem, and Changbin's
> following fix for gvt context notification.

Pulled to drm-intel-fixes, thanks.

BR,
Jani.

>
> Thanks.
>
> --
> The following changes since commit 2958b9013fcbabeeba221161d0712f5259f1e15d:
>
>   drm/i915/gvt: Fix gvt scheduler interval time (2017-03-17 16:46:45 +0800)
>
> are available in the git repository at:
>
>   https://github.com/01org/gvt-linux.git tags/gvt-fixes-2017-03-23
>
> for you to fetch changes up to bc2d4b62db67f817b09c782219996630e9c2f5e2:
>
>   drm/i915/gvt: Use force single submit flag to distinguish gvt request from i915 request (2017-03-22 13:18:56 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2017-03-23
>
> - KVM reference fix from Alex
> - shadow gtt entry partial update fix from Xiaoguang
> - gvt context notification check (Changbin)
> - other misc fixes.
>
> ----------------------------------------------------------------
> Alex Williamson (1):
>       drm/i915/kvmgt: Hold struct kvm reference
>
> Changbin Du (1):
>       drm/i915/gvt: Use force single submit flag to distinguish gvt request from i915 request
>
> Chuanxiao Dong (1):
>       drm/i915/gvt: fix wrong offset when loading RCS mocs
>
> Pei Zhang (1):
>       drm/i915/gvt: add write handler for mmio mbctl
>
> Xiaoguang Chen (1):
>       drm/i915/gvt: set shadow entry to scratch page while p2m failed
>
> Xu Han (1):
>       drm/i915/gvt: Fix guest fail to read EDID leading to black guest console issue.
>
>  drivers/gpu/drm/i915/gvt/edid.c      |  3 ++-
>  drivers/gpu/drm/i915/gvt/gtt.c       |  8 ++++++--
>  drivers/gpu/drm/i915/gvt/handlers.c  | 10 +++++++++-
>  drivers/gpu/drm/i915/gvt/kvmgt.c     |  2 ++
>  drivers/gpu/drm/i915/gvt/render.c    |  2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c |  7 ++++++-
>  6 files changed, 26 insertions(+), 6 deletions(-)

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-27  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  9:17 [GIT PULL] more GVT-g fixes for 4.11 Zhenyu Wang
2017-03-27  8:44 ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-24  6:12 Zhenyu Wang
2017-02-24 10:13 ` Jani Nikula
2017-02-15  7:29 Zhenyu Wang
2017-02-15 10:00 ` Jani Nikula

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=87zig785yd.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=zhenyuw@linux.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