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>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [GIT PULL] more GVT-g fixes for 4.13
Date: Tue, 11 Jul 2017 16:08:07 +0300 [thread overview]
Message-ID: <87a84bp1e0.fsf@nikula.org> (raw)
In-Reply-To: <20170711055333.jhrmvx6ilvg2qlnn@zhen-hp.sh.intel.com>
On Tue, 11 Jul 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> Still against dinf, here's current gvt fixes for 4.13.
Pulled, thanks.
BR,
Jani.
>
> Thanks.
> --
> The following changes since commit 7581d5ca2bb269cfc2ce2d0cb489aac513167f6b:
>
> drm/i915/fbdev: Check for existence of ifbdev->vma before operations (2017-07-10 10:33:03 +0300)
>
> are available in the git repository at:
>
> https://github.com/01org/gvt-linux.git tags/gvt-fixes-2017-07-11
>
> for you to fetch changes up to 0cf5ec41839d82ee7f8fbb47f137b7afc562b9f1:
>
> drm/i915/gvt: Use fence error from GVT request for workload status (2017-07-11 13:47:09 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2017-07-11
>
> - Revert "drm/i915/gvt: Fix possible recursive locking issue" (Chuanxiao),
> which is incomplete fix and it's actually VFIO issue, so revert.
> - remove unneeded scheduler mutex for performance fix (Weinan)
> - other misc error handling fix and cmd address audit
>
> ----------------------------------------------------------------
> Chuanxiao Dong (2):
> drm/i915/gvt: Revert "drm/i915/gvt: Fix possible recursive locking issue"
> drm/i915/gvt: Use fence error from GVT request for workload status
>
> Ping Gao (1):
> drm/i915/gvt: Audit the command buffer address
>
> Weinan Li (1):
> drm/i915/gvt: remove scheduler_mutex in per-engine workload_thread
>
> Zhou, Wenjia (1):
> drm/i915/gvt: Fix a memory leak in intel_gvt_init_gtt()
>
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 10 +++++++
> drivers/gpu/drm/i915/gvt/gtt.c | 2 ++
> drivers/gpu/drm/i915/gvt/gvt.h | 3 --
> drivers/gpu/drm/i915/gvt/kvmgt.c | 55 +++++++----------------------------
> drivers/gpu/drm/i915/gvt/scheduler.c | 28 ++++++++----------
> 5 files changed, 34 insertions(+), 64 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-07-11 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 5:53 [GIT PULL] more GVT-g fixes for 4.13 Zhenyu Wang
2017-07-11 13:08 ` 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=87a84bp1e0.fsf@nikula.org \
--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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.