intel-gfx.lists.freedesktop.org archive mirror
 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-fixes
Date: Wed, 15 Aug 2018 13:43:55 -0700	[thread overview]
Message-ID: <20180815204352.GA4070@intel.com> (raw)
In-Reply-To: <20180814073140.GJ22630@zhen-hp.sh.intel.com>

On Tue, Aug 14, 2018 at 03:31:40PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> This is initial gvt fixes for 4.19 with some accumulated fixes,
> pls check details below.

pulled, thanks.

> 
> Thanks
> --
> The following changes since commit 3237c0dbe21f8d2ca2feaa3891aff3619873cd30:
> 
>   drm/i915/kvmgt: Fix compilation error (2018-08-06 11:28:35 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-08-14
> 
> for you to fetch changes up to 7590ebb8b456464e48840a6d106a0c07de6d723a:
> 
>   drm/i915/gvt: fix memory leak in intel_vgpu_ioctl() (2018-08-14 15:27:12 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2018-08-14
> 
> - Fix an error code in gvt_dma_map_page() (Dan)
> - Fix off by one error in intel_vgpu_write_fence() (Dan)
> - Fix potential Spectre v1 (Gustavo)
> - Fix workload free in vgpu release (Henry)
> - Fix cleanup sequence in intel_gvt_clean_device (Henry)
> - dmabuf mutex init place fix (Henry)
> - possible memory leak in intel_vgpu_ioctl() err path (Yi)
> - return error on cmd access check failure (Yan)
> 
> ----------------------------------------------------------------
> Dan Carpenter (2):
>       drm/i915/kvmgt: fix an error code in gvt_dma_map_page()
>       drm/i915/gvt: Off by one in intel_vgpu_write_fence()
> 
> Gustavo A. R. Silva (1):
>       drm/i915/kvmgt: Fix potential Spectre v1
> 
> Hang Yuan (3):
>       drm/i915/gvt: free workload in vgpu release
>       drm/i915/gvt: fix cleanup sequence in intel_gvt_clean_device
>       drm/i915/gvt: initialize dmabuf mutex in vgpu_create
> 
> Yi Wang (1):
>       drm/i915/gvt: fix memory leak in intel_vgpu_ioctl()
> 
> Zhao Yan (1):
>       drm/i915/gvt: return error on cmd access
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c |  2 +-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c  |  2 +-
>  drivers/gpu/drm/i915/gvt/gvt.c         | 15 +++++++--------
>  drivers/gpu/drm/i915/gvt/gvt.h         |  4 +++-
>  drivers/gpu/drm/i915/gvt/kvmgt.c       | 26 ++++++++++++++++++--------
>  drivers/gpu/drm/i915/gvt/scheduler.c   |  7 ++++---
>  drivers/gpu/drm/i915/gvt/scheduler.h   |  3 +++
>  drivers/gpu/drm/i915/gvt/vgpu.c        | 23 +++++++++++++++++++++--
>  8 files changed, 58 insertions(+), 24 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:[~2018-08-15 20:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14  7:31 [PULL] gvt-next-fixes Zhenyu Wang
2018-08-15 20:43 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-07  9:05 Zhenyu Wang
2019-05-07 12:44 ` 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-11-12  6:20 Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-12-02  5:17 Zhenyu Wang

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=20180815204352.GA4070@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).