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] GVT-g fixes for drm-intel-next-fixes
Date: Fri, 30 Jun 2017 14:43:59 +0300 [thread overview]
Message-ID: <874luxbszk.fsf@intel.com> (raw)
In-Reply-To: <20170629065424.kxopjbvntuakbyz2@zhen-hp.sh.intel.com>
On Thu, 29 Jun 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi, this is current gvt fixes after 4.13 stuff got pulled in
> drm-intel-next. Mostly two race fixes and several virtual display
> fixes on BDW.
Pulled to drm-intel-next-fixes, thanks.
BR,
Jani.
>
> Thanks.
> --
> The following changes since commit e274086e473c0cbea18051ae0a78a05f8d658f47:
>
> drm/i915/gvt: clean up unsubmited workloads before destroying kmem cache (2017-05-24 10:33:37 +0800)
>
> are available in the git repository at:
>
> https://github.com/01org/gvt-linux.git tags/gvt-fixes-2017-06-29
>
> for you to fetch changes up to 5cd82b757795228516bf60a0552d1a40fa8adeb2:
>
> drm/i915/gvt: Make function dpy_reg_mmio_readx safe (2017-06-29 11:15:11 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2017-06-29
>
> - two race fixes for VFIO locks from Chuanxiao
> - virtual display fix for BDW from Xiong
>
> ----------------------------------------------------------------
> Changbin Du (1):
> drm/i915/gvt: Make function dpy_reg_mmio_readx safe
>
> Chuanxiao Dong (2):
> drm/i915/gvt: Fix possible recursive locking issue
> drm/i915/gvt: Fix inconsistent locks holding sequence
>
> Xiong Zhang (2):
> drm/i915/gvt: Set initial PORT_CLK_SEL vreg for BDW
> drm/i915/gvt: Don't read ADPA_CRT_HOTPLUG_MONITOR from host
>
> drivers/gpu/drm/i915/gvt/display.c | 22 ++++++++++++
> drivers/gpu/drm/i915/gvt/gvt.h | 3 ++
> drivers/gpu/drm/i915/gvt/handlers.c | 37 +++++++++++---------
> drivers/gpu/drm/i915/gvt/kvmgt.c | 69 +++++++++++++++++++++++++++++--------
> 4 files changed, 99 insertions(+), 32 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
prev parent reply other threads:[~2017-06-30 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:54 [GIT PULL] GVT-g fixes for drm-intel-next-fixes Zhenyu Wang
2017-06-30 11:43 ` Jani Nikula [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=874luxbszk.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;
as well as URLs for NNTP newsgroup(s).