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: [PULL] gvt-next-fixes
Date: Mon, 2 Dec 2019 13:17:11 +0800 [thread overview]
Message-ID: <20191202051711.GZ4196@zhen-hp.sh.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1344 bytes --]
Hi,
More gvt fixes for 5.5-rc. One is MI_ATOMIC cmd parser fix which
missed 5.4 and another two for CFL non-priv reg access fixes.
Thanks
--
The following changes since commit 83faaf074e6d1ca4d1441aded0d3f01bce413479:
drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08 11:08:07 +0800)
are available in the Git repository at:
https://github.com/intel/gvt-linux tags/gvt-next-fixes-2019-12-02
for you to fetch changes up to 92b1aa773fadb4e2a90ed5d3beecb422d568ad9a:
drm/i915/gvt: Fix cmd length check for MI_ATOMIC (2019-12-02 11:06:49 +0800)
----------------------------------------------------------------
gvt-next-fixes-2019-12-02
- Fix cmd parser for MI_ATOMIC (Zhenyu)
- Fix non-priv register access warning on CFL (Fred)
----------------------------------------------------------------
Gao, Fred (2):
drm/i915/gvt: Refine non privilege register address calucation
drm/i915/gvt: Update force-to-nonpriv register whitelist
Zhenyu Wang (1):
drm/i915/gvt: Fix cmd length check for MI_ATOMIC
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
drivers/gpu/drm/i915/gvt/handlers.c | 5 +++--
2 files changed, 6 insertions(+), 5 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
WARNING: multiple messages have this Message-ID (diff)
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-next-fixes
Date: Mon, 2 Dec 2019 13:17:11 +0800 [thread overview]
Message-ID: <20191202051711.GZ4196@zhen-hp.sh.intel.com> (raw)
Message-ID: <20191202051711.Z_QNDpfsVwea6Bct1GB12y_jH4ewQ_6YnIYyEa0uf2I@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1344 bytes --]
Hi,
More gvt fixes for 5.5-rc. One is MI_ATOMIC cmd parser fix which
missed 5.4 and another two for CFL non-priv reg access fixes.
Thanks
--
The following changes since commit 83faaf074e6d1ca4d1441aded0d3f01bce413479:
drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08 11:08:07 +0800)
are available in the Git repository at:
https://github.com/intel/gvt-linux tags/gvt-next-fixes-2019-12-02
for you to fetch changes up to 92b1aa773fadb4e2a90ed5d3beecb422d568ad9a:
drm/i915/gvt: Fix cmd length check for MI_ATOMIC (2019-12-02 11:06:49 +0800)
----------------------------------------------------------------
gvt-next-fixes-2019-12-02
- Fix cmd parser for MI_ATOMIC (Zhenyu)
- Fix non-priv register access warning on CFL (Fred)
----------------------------------------------------------------
Gao, Fred (2):
drm/i915/gvt: Refine non privilege register address calucation
drm/i915/gvt: Update force-to-nonpriv register whitelist
Zhenyu Wang (1):
drm/i915/gvt: Fix cmd length check for MI_ATOMIC
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
drivers/gpu/drm/i915/gvt/handlers.c | 5 +++--
2 files changed, 6 insertions(+), 5 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-12-02 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 5:17 Zhenyu Wang [this message]
2019-12-02 5:17 ` [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2019-12-05 6:11 ` Zhenyu Wang
2019-12-05 8:14 ` Joonas Lahtinen
2019-12-05 8:49 ` Zhenyu Wang
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 6:20 Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-09-06 5:42 Zhenyu Wang
2019-09-06 16:58 ` Rodrigo Vivi
2019-09-09 17:24 ` Rodrigo Vivi
2019-09-09 21:54 ` Vetter, Daniel
2019-09-09 22:35 ` Rodrigo Vivi
2019-09-10 2:36 ` Zhenyu Wang
2019-09-10 21:24 ` Vetter, Daniel
2019-05-07 9:05 Zhenyu Wang
2019-05-07 12:44 ` Joonas Lahtinen
2018-08-14 7:31 Zhenyu Wang
2018-08-15 20:43 ` 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=20191202051711.GZ4196@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;
as well as URLs for NNTP newsgroup(s).