Intel-GFX Archive on lore.kernel.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-fixes for 4.19-rc5
Date: Tue, 18 Sep 2018 08:53:10 -0700	[thread overview]
Message-ID: <20180918155310.GH2674@intel.com> (raw)
In-Reply-To: <20180918073349.GQ20737@zhen-hp.sh.intel.com>

On Tue, Sep 18, 2018 at 03:33:49PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's more gvt fixes for 4.19. Two more BXT fixes from Colin,
> one srcu locking fix and one fix for GGTT clear when destroy vGPU.

pulled, thanks.

> 
> p.s, I'll start my vacation from tomorrow. Wang Zhi will cover for gvt pull.
> 
> Thanks
> --
> The following changes since commit 792fab2c0d45758ad3d187bd252570d2bb627fa9:
> 
>   drm/i915/gvt: Fix the incorrect length of child_device_config issue (2018-09-06 11:17:38 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2018-09-18
> 
> for you to fetch changes up to 7759ca3aac79648d01c9edcb3b00503c02bec2f5:
> 
>   drm/i915/gvt: clear ggtt entries when destroy vgpu (2018-09-18 10:39:44 +0800)
> 
> ----------------------------------------------------------------
> gvt-fixes-2018-09-18
> 
> - Fix initial DPIO PHY register state for BXT (Colin)
> - BXT untracked GEN9_CLKGATE_DIS_4 warning fix (Colin)
> - Fix srcu lock for GFN valid check (Weinan)
> - Should clear GGTT entry value after vGPU destroy (Zhipeng)
> 
> ----------------------------------------------------------------
> Colin Xu (2):
>       drm/i915/gvt: Init PHY related registers for BXT
>       drm/i915/gvt: Add GEN9_CLKGATE_DIS_4 to default BXT mmio handler
> 
> Weinan Li (1):
>       drm/i915/gvt: request srcu_read_lock before checking if one gfn is valid
> 
> Zhipeng Gong (1):
>       drm/i915/gvt: clear ggtt entries when destroy vgpu
> 
>  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c    |  7 ++++++-
>  drivers/gpu/drm/i915/gvt/mmio.c     | 28 ++++++++++++++++++++++++++++
>  drivers/gpu/drm/i915/gvt/vgpu.c     |  1 +
>  4 files changed, 36 insertions(+), 1 deletion(-)
> 
> 
> -- 
> 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

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

  reply	other threads:[~2018-09-18 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  7:33 [PULL] gvt-fixes for 4.19-rc5 Zhenyu Wang
2018-09-18 15:53 ` Rodrigo Vivi [this message]
2018-09-19  6:34   ` Joonas Lahtinen
2018-09-25 17:51     ` Zhi 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=20180918155310.GH2674@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