All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"Yuan, Hang" <hang.yuan@intel.com>
Subject: [Intel-gfx] [PULL] gvt-gt-next
Date: Fri, 5 Feb 2021 15:30:57 +0800	[thread overview]
Message-ID: <20210205073057.GR2043@zhen-hp.sh.intel.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1607 bytes --]


Hi,

Here's more gvt next changes including ww locking fix from Zhi, and
replace to use i915 engine default state for GVT cmd parser init.
Those have all been verified without regression. Details below.

Thanks.
--
The following changes since commit 69b4b99842201bc24c98ba66b922d8879e190483:

  drm/i915/gvt: Add missing forward decl of intel_vgpu for HDRTEST (2021-01-21 15:51:21 +0200)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-gt-next-2020-02-05

for you to fetch changes up to e156285b120feaac6207e6bd3fa31d9ae8ffd80d:

  drm/i915/gvt: Purge dev_priv->gt (2021-02-05 15:28:36 +0800)

----------------------------------------------------------------
gvt-gt-next-2020-02-05

- GVT object ww locking fix (Zhi)
- One smatch fix for uninitialized return value (Dan)
- Use i915 engine's default state for GVT cmd parser init (Chris)
- Purge dev_priv->gt (Chris)

----------------------------------------------------------------
Chris Wilson (2):
      drm/i915/gvt: Parse default state to update reg whitelist
      drm/i915/gvt: Purge dev_priv->gt

Dan Carpenter (1):
      drm/i915/gvt: fix uninitialized return in intel_gvt_update_reg_whitelist()

Zhenyu Wang (1):
      Merge tag 'drm-intel-gt-next-2021-01-21-1' into gvt-gt-next

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

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 92 ++++++++---------------------------
 drivers/gpu/drm/i915/gvt/execlist.c   |  8 ++-
 drivers/gpu/drm/i915/gvt/scheduler.c  | 52 +++++++++++++++-----
 3 files changed, 64 insertions(+), 88 deletions(-)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

             reply	other threads:[~2021-02-05  7:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  7:30 Zhenyu Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-18  5:07 [Intel-gfx] [PULL] gvt-gt-next Zhenyu Wang
2021-01-20 12:21 ` Joonas Lahtinen
2021-01-20 15:55   ` Vivi, Rodrigo
2021-01-21  4:08   ` Zhenyu Wang
2021-01-21 13:15     ` Joonas Lahtinen
2021-01-21 13:53       ` Joonas Lahtinen
2021-01-21 14:17         ` 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=20210205073057.GR2043@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.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=rodrigo.vivi@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.