All of 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 5.1-rc1
Date: Thu, 7 Mar 2019 15:44:35 -0800	[thread overview]
Message-ID: <20190307234435.GB13329@intel.com> (raw)
In-Reply-To: <20190307060810.GT12380@zhen-hp.sh.intel.com>

On Thu, Mar 07, 2019 at 02:08:10PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-fixes for 5.1-rc1.

I'm kind of confused here. this should be -next-fixes right?

$ dim apply-pull drm-intel-next-fixes

Pulling https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-03-07 ...
From https://github.com/intel/gvt-linux
 * tag                         gvt-fixes-2019-03-07 -> FETCH_HEAD
dim: Pull request contains commits from drm/drm-fixes
dim: Please backmerge first
dim: ERROR: Issues in pull request detected, aborting

or am I missing something?

Thanks,
Rodrigo.

> This contains fixes for newer
> version of Windows driver, e.g fix parser for MI_FLUSH_DW and
> font render error. And with other stable fix in error path,
> fix unexpected workload submission when vGPU idle, etc. Details
> are below.
> 
> Thanks
> --
> The following changes since commit 0f75551216091223efe1f18295f655aff6415385:
> 
>   drm/i915/gvt: release shadow batch buffer and wa_ctx before destroy one workload (2019-01-23 13:58:46 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-03-07
> 
> for you to fetch changes up to 72aabfb862e40ee83c136c4f87877c207e6859b7:
> 
>   drm/i915/gvt: Add mutual lock for ppgtt mm LRU list (2019-03-04 14:45:28 +0800)
> 
> ----------------------------------------------------------------
> gvt-fixes-2019-03-07
> 
> - Fix MI_FLUSH_DW cmd parser on index check (Zhenyu)
> - Fix Windows guest font render error (Colin)
> - Fix unexpected workload submission for inactive vGPU (Weinan)
> - Fix incorrect workload submission in error path (Zhenyu)
> - Fix warning for shadow ppgtt mm reclaim list walk with locking (Zhenyu)
> 
> ----------------------------------------------------------------
> Colin Xu (1):
>       drm/i915/gvt: Add in context mmio 0x20D8 to gen9 mmio list
> 
> Weinan Li (1):
>       drm/i915/gvt: stop scheduling workload when vgpu is inactive
> 
> Zhenyu Wang (4):
>       drm/i915/gvt: Fix MI_FLUSH_DW parsing with correct index check
>       drm/i915/gvt: Don't submit request for error workload dispatch
>       drm/i915/gvt: Only assign ppgtt root at dispatch time
>       drm/i915/gvt: Add mutual lock for ppgtt mm LRU list
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  2 +-
>  drivers/gpu/drm/i915/gvt/gtt.c          | 14 +++++++++++++-
>  drivers/gpu/drm/i915/gvt/gtt.h          |  1 +
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  1 +
>  drivers/gpu/drm/i915/gvt/scheduler.c    | 28 ++++++++++++++++++++--------
>  5 files changed, 36 insertions(+), 10 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-03-07 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  6:08 [PULL] gvt-fixes for 5.1-rc1 Zhenyu Wang
2019-03-07 23:44 ` Rodrigo Vivi [this message]
2019-03-08  2:04   ` Zhenyu Wang
2019-03-08  2:47   ` 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=20190307234435.GB13329@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.