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: [PULL] gvt-next
Date: Tue, 13 Aug 2019 13:48:37 -0700	[thread overview]
Message-ID: <20190813204836.GA17273@intel.com> (raw)
In-Reply-To: <20190813100604.GG19140@zhen-hp.sh.intel.com>

On Tue, Aug 13, 2019 at 06:06:04PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-next stuff for next kernel which include several enhancement
> for cmd parser and batch buffer shadow, remove extra debugfs function
> return check, and with other misc changes like typo, static check fix,
> etc.

Pulled, Thanks

> 
> Thanks
> --
> The following changes since commit e0e712fe42ef67bdf45fc348767d1d0a4eeba77f:
> 
>   drm/i915: Update DRIVER_DATE to 20190730 (2019-07-30 11:50:24 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-08-13
> 
> for you to fetch changes up to 220b65d8009dff397a112ee560c297299ba5e423:
> 
>   drm/i915/gvt: Double check batch buffer size after copy (2019-08-13 17:55:06 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-2019-08-13
> 
> - Enhance command parser for extra length check (Fred)
> - remove debugfs function return check (Greg)
> - batch buffer end double check after shadow copy (Tina)
> - one typo fix (Zhenyu)
> - klocwork warning fix (Zhi)
> - use struct_size() helper (Gustavo)
> 
> ----------------------------------------------------------------
> Gao, Fred (3):
>       drm/i915/gvt: Utility for valid command length check
>       drm/i915/gvt: Add MI command valid length check
>       drm/i915/gvt: Add valid length check for MI variable commands
> 
> Greg Kroah-Hartman (1):
>       drm/i915/gvt: no need to check return value of debugfs_create functions
> 
> Gustavo A. R. Silva (1):
>       drm/i915/kvmgt: Use struct_size() helper
> 
> Tina Zhang (1):
>       drm/i915/gvt: Double check batch buffer size after copy
> 
> Zhenyu Wang (1):
>       drm/i915/gvt: Fix typo of VBLANK_TIMER_PERIOD
> 
> Zhi Wang (1):
>       drm/i915/gvt: factor out tlb and mocs register offset table
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 180 ++++++++++++++++++++++++++------
>  drivers/gpu/drm/i915/gvt/debugfs.c      |  47 ++-------
>  drivers/gpu/drm/i915/gvt/gvt.c          |   4 +-
>  drivers/gpu/drm/i915/gvt/gvt.h          |   8 +-
>  drivers/gpu/drm/i915/gvt/interrupt.c    |   4 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c        |  15 +--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  57 ++++++----
>  drivers/gpu/drm/i915/gvt/vgpu.c         |   4 +-
>  8 files changed, 212 insertions(+), 107 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

  reply	other threads:[~2019-08-13 20:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 10:06 [PULL] gvt-next Zhenyu Wang
2019-08-13 20:48 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-09  4:05 Zhenyu Wang
2019-04-16  7:29 ` Joonas Lahtinen
2019-04-16  8:48   ` Zhenyu Wang
2019-04-17  6:40     ` Joonas Lahtinen
2019-02-01  6:15 Zhenyu Wang
2019-02-01 17:04 ` Rodrigo Vivi
2019-01-24  5:40 Zhenyu Wang
2019-01-31 18:02 ` Rodrigo Vivi
2018-06-19  9:00 Zhenyu Wang
2018-06-19 21:46 ` 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=20190813204836.GA17273@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