public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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
Date: Wed, 26 Feb 2020 15:10:00 -0800	[thread overview]
Message-ID: <20200226231000.GA2094112@intel.com> (raw)
In-Reply-To: <20200226103840.GD10413@zhen-hp.sh.intel.com>

On Wed, Feb 26, 2020 at 06:38:40PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-next pull. Mostly for cleanup and kvmgt specific struct
> has been moved to its own module, also enable VFIO edid for all platform
> including CML. Pls see details below.

pulled, thanks

> 
> Thanks
> --
> The following changes since commit e24bcd34c1dd7dabde4a8546920537f7137e3c5f:
> 
>   drm/i915/dp: Add all tiled and port sync conns to modeset (2020-02-20 13:55:02 +0530)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-02-26
> 
> for you to fetch changes up to a8bb49b64c4f4284fb36169bdd9fc6efd62eb26a:
> 
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable (2020-02-25 16:13:04 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-2020-02-26
> 
> - Enable VFIO edid for all platform (Zhenyu)
> - Code cleanup for attr group and unused vblank complete (Zhenyu, Julian)
> - Make gvt oblivious of kvmgt data structures (Julian)
> - Make WARN* drm specific (Pankaj)
> 
> ----------------------------------------------------------------
> Julian Stecklina (2):
>       drm/i915/gvt: remove unused vblank_done completion
>       drm/i915/gvt: make gvt oblivious of kvmgt data structures
> 
> Pankaj Bharadiya (2):
>       drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
>       drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
> 
> Tina Zhang (1):
>       drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable
> 
> Zhenyu Wang (3):
>       drm/i915/gvt: remove unused type attributes
>       drm/i915/gvt: Enable vfio edid for all GVT supported platform
>       Merge drm-intel-next-queued into gvt-next
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  |   6 +-
>  drivers/gpu/drm/i915/gvt/cfg_space.c    |  23 ++-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/display.c      |   6 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.c       |   4 +-
>  drivers/gpu/drm/i915/gvt/edid.c         |  19 +-
>  drivers/gpu/drm/i915/gvt/gtt.c          |  21 ++-
>  drivers/gpu/drm/i915/gvt/gvt.c          |   8 +-
>  drivers/gpu/drm/i915/gvt/gvt.h          |  37 +---
>  drivers/gpu/drm/i915/gvt/handlers.c     |  22 ++-
>  drivers/gpu/drm/i915/gvt/interrupt.c    |  15 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c        | 303 +++++++++++++++++++-------------
>  drivers/gpu/drm/i915/gvt/mmio.c         |  30 ++--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   6 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c    |   6 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c         |  10 +-
>  16 files changed, 304 insertions(+), 216 deletions(-)
> 
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-02-26 23:09 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 10:38 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2020-02-26 11:58 ` Jani Nikula
2020-02-27  9:31   ` Zhenyu Wang
2020-02-26 23:10 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-10  8:19 Zhenyu Wang
2020-03-10 22:50 ` Rodrigo Vivi
2020-04-22  5:12 Zhenyu Wang
2020-04-26  2:46 ` Zhenyu Wang
2020-04-30 12:38   ` Joonas Lahtinen
2020-05-12  9:40 Zhenyu Wang
2020-05-14 16:04 ` Joonas Lahtinen
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-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-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
2021-03-16  7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
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
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-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

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=20200226231000.GA2094112@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