All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	igvt-g-dev <igvt-g-dev@lists.01.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [GIT PULL] GVT-g fixes for 4.10-rc4
Date: Tue, 10 Jan 2017 10:21:53 +0200	[thread overview]
Message-ID: <878tqje34u.fsf@intel.com> (raw)
In-Reply-To: <20170110052427.bt63b6qgbl64xnbc@zhen-hp.sh.intel.com>

On Tue, 10 Jan 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> Please pull GVT-g device model fixes for rc4. This is based on rc3 with
> new vfio/mdev interface change.

Thanks, pulled to drm-intel-fixes.

BR,
Jani.

>
> Thanks.
> ---
>
> The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
>
>   Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
>
> are available in the git repository at:
>
>   https://github.com/01org/gvt-linux.git tags/gvt-fixes-2017-01-10
>
> for you to fetch changes up to 9631739f8196ec80b5d9bf955f79b711490c0205:
>
>   drm/i915/gvt: cleanup GFP flags (2017-01-09 17:31:05 +0800)
>
> ----------------------------------------------------------------
> Changbin Du (5):
>       drm/i915/gvt: fix error handing of tlb_control emulation
>       drm/i915/gvt: fix return value in mul_force_wake_write
>       drm/i915/gvt: always use readq and writeq
>       drm/i915/gvt: fix use after free for workload
>       drm/i915/gvt: dec vgpu->running_workload_num after the workload is really done
>
> Jike Song (5):
>       drm/i915/gvt: init/destroy vgpu_idr properly
>       drm/i915/gvt: destroy the allocated idr on vgpu creating failures
>       drm/i915/gvt: cleanup opregion memory allocation code
>       drm/i915/gvt/kvmgt: return meaningful error for vgpu creating failure
>       drm/i915/gvt: cleanup GFP flags
>
> Nicolas Iooss (1):
>       drm/i915/gvt: verify functions types in new_mmio_info()
>
> Pei Zhang (1):
>       drm/i915/gvt: print correct value for untracked mmio
>
> Zhenyu Wang (2):
>       drm/i915/gvt: adjust high memory size for default vGPU type
>       drm/i915/gvt: remove duplicated definition
>
>  drivers/gpu/drm/i915/gvt/aperture_gm.c |  7 -----
>  drivers/gpu/drm/i915/gvt/gtt.c         | 54 +++++++++++-----------------------
>  drivers/gpu/drm/i915/gvt/gvt.c         |  8 ++++-
>  drivers/gpu/drm/i915/gvt/handlers.c    | 13 ++++----
>  drivers/gpu/drm/i915/gvt/kvmgt.c       | 14 ++++++---
>  drivers/gpu/drm/i915/gvt/mmio.c        | 31 +++++++++----------
>  drivers/gpu/drm/i915/gvt/opregion.c    |  8 ++---
>  drivers/gpu/drm/i915/gvt/reg.h         |  3 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c   | 14 ++++-----
>  drivers/gpu/drm/i915/gvt/vgpu.c        |  8 +++--
>  10 files changed, 73 insertions(+), 87 deletions(-)

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-01-10  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  5:24 [GIT PULL] GVT-g fixes for 4.10-rc4 Zhenyu Wang
2017-01-10  8:21 ` Jani Nikula [this message]

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=878tqje34u.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=igvt-g-dev@lists.01.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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.