From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.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: [PULL] gvt-next for 4.20
Date: Tue, 4 Sep 2018 11:01:54 +0800 [thread overview]
Message-ID: <20180904030154.GG20737@zhen-hp.sh.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2192 bytes --]
Hi,
Here's initial gvt-next for 4.20 with two optimization for
guest context shadowing and command parser, and with W=1 build fixes.
Thanks
--
The following changes since commit 279ce5d117078ee8ea40c40199399889981fd808:
drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 +0800)
are available in the Git repository at:
https://github.com/intel/gvt-linux.git tags/gvt-next-2018-09-04
for you to fetch changes up to 69ca5af4ff9a3ff96e4595c2b7522c01a2641779:
drm/i915/gvt: Move some MMIO definitions to reg.h (2018-08-07 10:40:11 +0800)
----------------------------------------------------------------
gvt-next-2018-09-04
- guest context shadow optimization for restore inhibit one (Yan)
- cmd parser optimization (Yan)
- W=1 warning fixes (Zhenyu)
----------------------------------------------------------------
Zhao Yan (2):
drm/i915/gvt: add a fastpath for cmd parsing on MI_NOOP
drm/i915/gvt: only copy the first page for restore inhibit context
Zhenyu Wang (3):
drm/i915/gvt: make dma map/unmap kvmgt functions as static
drm/i915/gvt: Fix function comment doc errors
drm/i915/gvt: Move some MMIO definitions to reg.h
drivers/gpu/drm/i915/gvt/cfg_space.c | 12 +++++++
drivers/gpu/drm/i915/gvt/cmd_parser.c | 11 +++++-
drivers/gpu/drm/i915/gvt/display.c | 1 +
drivers/gpu/drm/i915/gvt/edid.c | 9 +++++
drivers/gpu/drm/i915/gvt/gtt.c | 9 +++--
drivers/gpu/drm/i915/gvt/gvt.c | 3 +-
drivers/gpu/drm/i915/gvt/handlers.c | 1 +
drivers/gpu/drm/i915/gvt/kvmgt.c | 4 +--
drivers/gpu/drm/i915/gvt/mmio.c | 3 +-
drivers/gpu/drm/i915/gvt/mmio_context.c | 13 -------
drivers/gpu/drm/i915/gvt/mmio_context.h | 3 ++
drivers/gpu/drm/i915/gvt/opregion.c | 1 -
drivers/gpu/drm/i915/gvt/page_track.c | 2 ++
drivers/gpu/drm/i915/gvt/reg.h | 9 +++++
drivers/gpu/drm/i915/gvt/scheduler.c | 64 +++++++++++++++++----------------
15 files changed, 92 insertions(+), 53 deletions(-)
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- 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:[~2018-09-04 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 3:01 Zhenyu Wang [this message]
2018-09-06 13:11 ` [PULL] gvt-next for 4.20 Joonas Lahtinen
2018-09-07 2:47 ` 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=20180904030154.GG20737@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox