From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.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
Date: Wed, 5 Jun 2019 16:49:03 +0800 [thread overview]
Message-ID: <20190605084903.GX9684@zhen-hp.sh.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1728 bytes --]
Hi,
More gvt fixes for 5.2-rc. This fixed one regression when enabling
debug build of i915 guest, guest ring state fix after execution
for hang check, and with two misc fixes from klocwork check.
Thanks
--
The following changes since commit 3035e8cd6c316cb633b45bc9b38052ba2dfd299b:
drm/i915/gvt: Fix cmd length of VEB_DI_IECP (2019-05-30 11:31:43 +0800)
are available in the Git repository at:
https://github.com/intel/gvt-linux tags/gvt-fixes-2019-06-05
for you to fetch changes up to 15e7f52a4596b496ce3da2fa4c1f94c6fb0023f2:
drm/i915/gvt: save RING_HEAD into vreg when vgpu switched out (2019-06-03 13:18:36 +0800)
----------------------------------------------------------------
gvt-fixes-2019-06-05
- Fix i915 guest debug build for register command access (Weinan)
- Fix guest ring state after execution for hangcheck (Xiaolin)
- klocwork static check fixes (Alek)
----------------------------------------------------------------
Aleksei Gimbitskii (2):
drm/i915/gvt: Check if cur_pt_type is valid
drm/i915/gvt: Assign NULL to the pointer after memory free.
Weinan Li (1):
drm/i915/gvt: add F_CMD_ACCESS flag for wa regs
Xiaolin Zhang (1):
drm/i915/gvt: save RING_HEAD into vreg when vgpu switched out
drivers/gpu/drm/i915/gvt/gtt.c | 12 +++++++++++-
drivers/gpu/drm/i915/gvt/handlers.c | 13 +++++++------
drivers/gpu/drm/i915/gvt/reg.h | 2 ++
drivers/gpu/drm/i915/gvt/scheduler.c | 25 +++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/scheduler.h | 1 +
5 files changed, 46 insertions(+), 7 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: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-06-05 8:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 8:49 Zhenyu Wang [this message]
2019-06-06 12:04 ` [PULL] gvt-fixes Joonas Lahtinen
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05 3:21 ` Zhenyu Wang
2019-11-22 3:33 Zhenyu Wang
2019-11-12 6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-08-13 9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-07-23 9:29 Zhenyu Wang
2019-07-29 3:33 ` Zhenyu Wang
2019-07-29 11:05 ` Jani Nikula
2019-07-30 7:00 ` Zhenyu Wang
2019-07-30 8:33 ` Jani Nikula
2019-06-19 6:22 Zhenyu Wang
2019-06-19 7:56 ` Jani Nikula
2019-05-29 9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30 3:41 ` Zhenyu Wang
2019-05-31 8:16 ` Joonas Lahtinen
2019-05-21 6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11 6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-04-02 9:40 Zhenyu Wang
2019-04-04 0:12 ` Rodrigo Vivi
2019-04-04 0:32 ` Zhenyu Wang
2019-04-04 1:03 ` Rodrigo Vivi
2019-04-04 0:39 ` Zhenyu Wang
2019-03-21 3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24 5:48 Zhenyu Wang
2019-01-31 9:45 ` 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=20190605084903.GX9684@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.