From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes
Date: Tue, 23 Feb 2021 09:42:30 -0500 [thread overview]
Message-ID: <YDUUVt0chYrFyUQQ@intel.com> (raw)
In-Reply-To: <20210222083402.GD1551@zhen-hp.sh.intel.com>
On Mon, Feb 22, 2021 at 04:34:02PM +0800, Zhenyu Wang wrote:
>
> Hi,
>
> Looks last gvt pull missed -gt-next window before CNY holiday.
> So here're left three changes for fixing ww locking, cmd parser
> fix for i915 state use and one left cleanup fix.
no problem at all. I believe we still have time.
pulled now.
Happy New Year!
>
> Thanks!
> --
> The following changes since commit 81ce8f04aa96f7f6cae05770f68b5d15be91f5a2:
>
> drm/i915/gt: Correct surface base address for renderclear (2021-02-17 06:19:04 -0500)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-02-22
>
> for you to fetch changes up to 67f1120381df022a7016f4acc8d4880da9a66c03:
>
> drm/i915/gvt: Introduce per object locking in GVT scheduler. (2021-02-22 16:42:14 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fixes-2021-02-22
>
> - Fix to use i915 default state for cmd parser on all engines (Chris)
> - Purge dev_priv->gt (Chris)
> - Fix gvt object ww locking (Zhi)
>
> ----------------------------------------------------------------
> Chris Wilson (2):
> drm/i915/gvt: Parse default state to update reg whitelist
> drm/i915/gvt: Purge dev_priv->gt
>
> Zhi Wang (1):
> drm/i915/gvt: Introduce per object locking in GVT scheduler.
>
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 93 ++++++++---------------------------
> drivers/gpu/drm/i915/gvt/execlist.c | 8 ++-
> drivers/gpu/drm/i915/gvt/scheduler.c | 52 +++++++++++++++-----
> 3 files changed, 64 insertions(+), 89 deletions(-)
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-02-23 14:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 8:34 [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 7:47 Zhenyu Wang
2023-02-23 8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29 8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21 9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2020-12-25 2:20 Zhenyu Wang
2021-01-05 7:54 ` Zhenyu Wang
2021-01-05 8:36 ` Jani Nikula
2021-01-05 20:44 ` Rodrigo Vivi
2020-08-05 8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28 3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31 7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03 3:05 ` Zhenyu Wang
2020-04-03 17:50 ` Rodrigo Vivi
2020-04-07 8:02 ` Zhenyu Wang
2020-04-07 13:35 ` Rodrigo Vivi
2020-04-07 13:53 ` Jani Nikula
2020-04-07 23:36 ` Zhenyu Wang
2019-12-02 5:17 Zhenyu Wang
2019-12-02 5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05 6:11 ` Zhenyu Wang
2019-12-05 8:14 ` Joonas Lahtinen
2019-12-05 8:49 ` Zhenyu Wang
2019-11-12 6:20 Zhenyu Wang
2019-11-12 6:20 ` [Intel-gfx] " Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-11-20 11:25 ` [Intel-gfx] " Joonas Lahtinen
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=YDUUVt0chYrFyUQQ@intel.com \
--to=rodrigo.vivi@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=zhenyuw@linux.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).