All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Yuan, Hang" <hang.yuan@intel.com>,
	"Xu, Terrence" <terrence.xu@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [GIT PULL] gvt-fixes for 4.15-rc3
Date: Thu, 07 Dec 2017 14:08:16 +0200	[thread overview]
Message-ID: <1512648496.4586.28.camel@linux.intel.com> (raw)
In-Reply-To: <20171206075105.wlh2ojubjczlstox@zhen-hp.sh.intel.com>

Hi,

Pulled these, I will give it a final go with CI and send the pull forward. Thanks.

Regards, Joonas

On Wed, 2017-12-06 at 15:51 +0800, Zhenyu Wang wrote:
> Hi,
> 
> Here's gvt-fixes for 4.15-rc3 with several fixes backported.
> 
> thanks
> --
> The following changes since commit b721b65af4eb46df6a1d9e34b14003225e403565:
> 
>   drm/i915/gvt: Correct ADDR_4K/2M/1G_MASK definition (2017-11-28 17:24:30 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2017-12-06
> 
> for you to fetch changes up to 11474e9091cf2002e948647fd9f63a7f027e488a:
> 
>   drm/i915/gvt: set max priority for gvt context (2017-12-06 11:38:21 +0800)
> 
> ----------------------------------------------------------------
> gvt-fixes-2017-12-06
> 
> - Fix invalid hw reg read value for vGPU (Xiong)
> - Fix qemu warning on PCI ROM bar missing (Changbin)
> - Workaround preemption regression (Zhenyu)
> 
> ----------------------------------------------------------------
> Changbin Du (1):
>       drm/i915/gvt: Emulate PCI expansion ROM base address register
> 
> Xiong Zhang (1):
>       drm/i915/gvt: Limit read hw reg to active vgpu
> 
> Zhenyu Wang (2):
>       drm/i915/gvt: Don't mark vgpu context as inactive when preempted
>       drm/i915/gvt: set max priority for gvt context
> 
> Zhi Wang (1):
>       drm/i915/gvt: Export intel_gvt_render_mmio_to_ring_id()
> 
>  drivers/gpu/drm/i915/gvt/cfg_space.c | 21 ++++++++++++++++
>  drivers/gpu/drm/i915/gvt/handlers.c  | 47 ++++++++++++++++++++++++++++--------
>  drivers/gpu/drm/i915/gvt/mmio.h      |  2 ++
>  drivers/gpu/drm/i915/gvt/scheduler.c | 22 ++++++++++++++++-
>  4 files changed, 81 insertions(+), 11 deletions(-)
> 
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-12-07 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  7:51 [GIT PULL] gvt-fixes for 4.15-rc3 Zhenyu Wang
2017-12-07 12:08 ` Joonas Lahtinen [this message]
2017-12-08  9:32 ` Daniel Vetter

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=1512648496.4586.28.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.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=rodrigo.vivi@intel.com \
    --cc=terrence.xu@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.