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-fixes for 4.19
Date: Tue, 4 Sep 2018 10:54:37 +0800 [thread overview]
Message-ID: <20180904025437.GE20737@zhen-hp.sh.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2046 bytes --]
Hi,
Here's current gvt-fixes for 4.19 with more BXT fixes,
two guest warning fixes, dmabuf format mod fix and one
for recent multiple VM timeout failure.
Thanks
--
The following changes since commit 80ab316901bc4ae6dd0b5903dbe22766307eac9b:
drm/i915/audio: Hook up component bindings even if displays are disabled (2018-08-29 14:11:53 -0700)
are available in the Git repository at:
https://github.com/intel/gvt-linux.git tags/gvt-fixes-2018-09-04
for you to fetch changes up to 54ff01fd0d44b9681615f77c15fe9ea6dfadb501:
drm/i915/gvt: Give new born vGPU higher scheduling chance (2018-09-03 14:28:23 +0800)
----------------------------------------------------------------
gvt-fixes-2018-09-04
- two BXT virtual display emulation fixes (Colin)
- gen9 dbuf guest warning fix (Xiaolin)
- vgpu close pm warning fix (Hang)
- dmabuf format_mod fix (Zhenyu)
- multiple VM guest failure fix for scheduling (Zhenyu)
----------------------------------------------------------------
Colin Xu (2):
drm/i915/gvt: Make correct handling to vreg BXT_PHY_CTL_FAMILY
drm/i915/gvt: Handle GEN9_WM_CHICKEN3 with F_CMD_ACCESS.
Hang Yuan (1):
drm/i915/gvt: move intel_runtime_pm_get out of spin_lock in stop_schedule
Xiaolin Zhang (1):
drm/i915/gvt: emulate gen9 dbuf ctl register access
Zhenyu Wang (2):
drm/i915/gvt: Fix drm_format_mod value for vGPU plane
drm/i915/gvt: Give new born vGPU higher scheduling chance
drivers/gpu/drm/i915/gvt/dmabuf.c | 33 ++++++++++++++++++++++-------
drivers/gpu/drm/i915/gvt/fb_decoder.c | 5 ++---
drivers/gpu/drm/i915/gvt/fb_decoder.h | 2 +-
drivers/gpu/drm/i915/gvt/handlers.c | 33 +++++++++++++++++++++++------
drivers/gpu/drm/i915/gvt/mmio_context.c | 2 --
drivers/gpu/drm/i915/gvt/sched_policy.c | 37 ++++++++++++++++++++++++++-------
6 files changed, 86 insertions(+), 26 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 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 2:54 Zhenyu Wang [this message]
2018-09-04 4:36 ` [PULL] gvt-fixes for 4.19 Rodrigo Vivi
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=20180904025437.GE20737@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