public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Wang, Zhi A" <zhi.a.wang@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Yuan, Hang" <hang.yuan@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Wang, Zhi A" <zhi.a.wang@intel.com>
Subject: [Intel-gfx] [PULL] topic/gvt-ww-lock
Date: Tue, 22 Sep 2020 14:51:42 +0300	[thread overview]
Message-ID: <4b78ef66-a74f-9156-62fb-bb733947b57e@intel.com> (raw)


Hi,

Here's the patch which introduces GVT-g ww lock support against 
drm-intel-gt-next branch.

Thanks

--

The following changes since commit 4316b19dee27cc5cd34a95fdbc0a3a5237507701:

   drm/i915: Fix uninitialised variable in intel_context_create_request. 
(2020-09-21 11:09:46 +0200)

are available in the git repository at:

   https://github.com/intel/gvt-linux.git tags/gvt-ww-lock-09-22-2020

for you to fetch changes up to e1b49ae155451aaa039eeb23fce808c71a038283:

   drm/i915/gvt: Introduce per object locking in GVT scheduler. 
(2020-09-22 12:09:56 +0300)

----------------------------------------------------------------
gvt-ww-lock-09-22-2020:

- Introduce ww lock support into GVT-g.

----------------------------------------------------------------
Zhi Wang (1):
       drm/i915/gvt: Introduce per object locking in GVT scheduler.

  drivers/gpu/drm/i915/gvt/scheduler.c | 68 
++++++++++++++++++++++++++++++------
  1 file changed, 57 insertions(+), 11 deletions(-)

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

             reply	other threads:[~2020-09-22 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 11:51 Wang, Zhi A [this message]
2020-09-30 11:54 ` [Intel-gfx] [PULL] topic/gvt-ww-lock Maarten Lankhorst
2020-11-08  7:51   ` Wang, Zhi A

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=4b78ef66-a74f-9156-62fb-bb733947b57e@intel.com \
    --to=zhi.a.wang@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=joonas.lahtinen@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