public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@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: Re: [Intel-gfx] [PULL] gvt-next
Date: Sun, 26 Apr 2020 10:46:19 +0800	[thread overview]
Message-ID: <20200426024619.GA18545@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20200422051230.GH11247@zhen-hp.sh.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2169 bytes --]

On 2020.04.22 13:12:30 +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's current gvt-next. This removes left non-upstream xen support bits
> which will be kept out of tree instead. And several guest context shadow
> optimizations from Yan.
> 
> Thanks
> --

Ping for merge..

> 
> The following changes since commit a61ac1e75105a077ec1efd6923ae3c619f862304:
> 
>   drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06 10:08:10 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-04-22
> 
> for you to fetch changes up to fb55c735522352704c35d899d0b253453cf0e799:
> 
>   drm/i915/gvt: skip populate shadow context if guest context not changed (2020-04-17 17:31:22 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-2020-04-22
> 
> - remove non-upstream xen support bits (Christoph)
> - guest context shadow copy optimization (Yan)
> - guest context tracking for shadow skip optimization (Yan)
> 
> ----------------------------------------------------------------
> Christoph Hellwig (1):
>       i915/gvt: remove unused xen bits
> 
> Yan Zhao (3):
>       drm/i915/gvt: access shadow ctx via its virtual address directly
>       drm/i915/gvt: combine access to consecutive guest context pages
>       drm/i915/gvt: skip populate shadow context if guest context not changed
> 
>  drivers/gpu/drm/i915/gvt/gtt.c       |  15 +++++
>  drivers/gpu/drm/i915/gvt/gvt.c       |   1 -
>  drivers/gpu/drm/i915/gvt/gvt.h       |   5 ++
>  drivers/gpu/drm/i915/gvt/hypercall.h |   2 -
>  drivers/gpu/drm/i915/gvt/scheduler.c | 127 ++++++++++++++++++++++++++---------
>  5 files changed, 114 insertions(+), 36 deletions(-)
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev


-- 
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

  reply	other threads:[~2020-04-26  3:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  5:12 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2020-04-26  2:46 ` Zhenyu Wang [this message]
2020-04-30 12:38   ` Joonas Lahtinen
  -- strict thread matches above, loose matches on Subject: below --
2022-11-11  8:59 Zhenyu Wang
2022-11-15 15:36 ` Rodrigo Vivi
2022-11-17  3:02   ` Zhenyu Wang
2022-11-17  3:37     ` Vivi, Rodrigo
2022-11-17  5:28       ` Zhenyu Wang
2022-11-17  6:41       ` Zhenyu Wang
2022-11-17 13:49         ` Rodrigo Vivi
2022-04-26  7:58 Wang, Zhi A
2022-04-26  8:37 ` Jani Nikula
2022-04-26  8:38   ` Wang, Zhi A
2022-04-26  8:42   ` Wang, Zhi A
2022-04-26 11:52     ` Jason Gunthorpe
2022-04-28 21:35       ` Alex Williamson
2022-04-28 21:48         ` Alex Williamson
2022-04-26 15:53 ` Jason Gunthorpe
2022-04-26 16:58   ` Wang, Zhi A
2022-04-26 19:19     ` Robert Beckett
2022-04-20  8:04 Wang, Zhi A
2022-04-20 12:13 ` Jason Gunthorpe
2022-04-20 14:41   ` Wang, Zhi A
2022-04-20 15:02     ` Jason Gunthorpe
2022-04-20 16:13       ` Wang, Zhi A
2021-03-16  7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
2020-11-23  9:05 Zhenyu Wang
2020-11-23  9:32 ` Joonas Lahtinen
2020-11-24  3:13   ` Zhenyu Wang
2020-11-24  9:48     ` Jani Nikula
2020-11-27 13:26     ` Joonas Lahtinen
2020-09-10  5:37 Zhenyu Wang
2020-09-11 23:58 ` Rodrigo Vivi
2020-09-14  2:34   ` Zhenyu Wang
2020-09-14 18:39     ` Vivi, Rodrigo
2020-07-20  8:05 Zhenyu Wang
2020-07-21 11:04 ` Joonas Lahtinen
2020-07-22  0:42   ` Zhenyu Wang
2020-07-27 16:39     ` Vivi, Rodrigo
2020-07-28  3:18       ` Zhenyu Wang
2020-05-12  9:40 Zhenyu Wang
2020-05-14 16:04 ` Joonas Lahtinen
2020-03-10  8:19 Zhenyu Wang
2020-03-10 22:50 ` Rodrigo Vivi
2020-02-26 10:38 Zhenyu Wang
2020-02-26 11:58 ` Jani Nikula
2020-02-27  9:31   ` Zhenyu Wang
2020-02-26 23:10 ` 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=20200426024619.GA18545@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