From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Jani Nikula <jani.nikula@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: Mon, 18 Jan 2021 13:07:39 +0800 [thread overview]
Message-ID: <20210118050739.GY15982@zhen-hp.sh.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2022 bytes --]
Hi,
This is GVT next for 5.12 against drm-intel-gt-next which is mostly
for cmd parser enhancement which adds extra check on register load
depending on initial context and handles vGPU register state
accordingly.
Thanks.
--
The following changes since commit fe7bcfaeb2b775f257348dc7b935f8e80eef3e7d:
drm/i915/gt: Refactor heartbeat request construction and submission (2020-12-24 18:07:26 +0000)
are available in the Git repository at:
https://github.com/intel/gvt-linux tags/gvt-gt-next-2021-01-18
for you to fetch changes up to 02dd2b12a685944c4d52c569d05f636372a7b6c7:
drm/i915/gvt: unify lri cmd handler and mmio handlers (2020-12-25 11:16:32 +0800)
----------------------------------------------------------------
gvt-gt-next-2021-01-18
- GVT cmd parser enhancement against guest context (Yan)
----------------------------------------------------------------
Yan Zhao (11):
drm/i915/gvt: parse init context to update cmd accessible reg whitelist
drm/i915/gvt: scan VM ctx pages
drm/i915/gvt: filter cmds "srm" and "lrm" in cmd_handler
drm/i915/gvt: filter cmds "lrr-src" and "lrr-dst" in cmd_handler
drm/i915/gvt: filter cmd "pipe-ctrl" in cmd_handler
drm/i915/gvt: export find_mmio_info
drm/i915/gvt: make width of mmio_attribute bigger
drm/i915/gvt: introduce a new flag F_CMD_WRITE_PATCH
drm/i915/gvt: statically set F_CMD_WRITE_PATCH flag
drm/i915/gvt: update F_CMD_WRITE_PATCH flag when parsing init ctx
drm/i915/gvt: unify lri cmd handler and mmio handlers
drivers/gpu/drm/i915/gvt/cmd_parser.c | 335 +++++++++++++++++++++++++++-------
drivers/gpu/drm/i915/gvt/cmd_parser.h | 4 +
drivers/gpu/drm/i915/gvt/gvt.h | 37 +++-
drivers/gpu/drm/i915/gvt/handlers.c | 15 +-
drivers/gpu/drm/i915/gvt/mmio.h | 3 +
drivers/gpu/drm/i915/gvt/reg.h | 2 +
drivers/gpu/drm/i915/gvt/scheduler.c | 22 ++-
drivers/gpu/drm/i915/gvt/vgpu.c | 4 +-
8 files changed, 339 insertions(+), 83 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
next reply other threads:[~2021-01-18 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 5:07 Zhenyu Wang [this message]
2021-01-20 12:21 ` [Intel-gfx] [PULL] gvt-gt-next 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
2021-02-05 7:30 Zhenyu Wang
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=20210118050739.GY15982@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.