From: Daniel Vetter <daniel@ffwll.ch>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
igvt-g-dev@lists.01.org, "Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [PULL] GVT-g device model core fixes
Date: Thu, 20 Oct 2016 15:30:45 +0200 [thread overview]
Message-ID: <20161020133045.GU20761@phenom.ffwll.local> (raw)
In-Reply-To: <20161020101325.cqhmgumhkck7tatb@zhen-hp.sh.intel.com>
On Thu, Oct 20, 2016 at 06:13:25PM +0800, Zhenyu Wang wrote:
>
> Hi,
>
> This is second pull request for GVT-g sub module which contains
> fixes for issues within first pull request.
>
> Regression test has been passed combining this new pull request
> with unmerged driver facilities to test for VMs.
>
> Thanks.
Pulled, thanks. Quick one: I think it'd be good to also pull in the
intel_gvt.h header into the kerneldocs, and document shared structs a bit.
But that's probably better done after the header cleanup has landed.
-Daniel
>
> --
> The following changes since commit 1140f9ed051011e06a2a15c73efe57ac0b0cdc8d:
>
> drm/i915/gvt: Fix build failure after intel_engine_cs change (2016-10-18 08:24:49 +0200)
>
> are available in the git repository at:
>
> https://github.com/01org/gvt-linux.git tags/gvt-next-fix-2016-10-20
>
> for you to fetch changes up to 19e6393fb5366a89705a62b3276ce42e990d12ce:
>
> drm/i915/gvt: do not ignore return value of create_scratch_page (2016-10-20 17:31:36 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fix-2016-10-20
>
> This contains fix for first pull request.
> - clean up header mess between i915 core and gvt
> - new MAINTAINERS item
> - new kernel-doc section
> - fix compiling warnings
> - gvt gem fix series from Chris
> - fix for i915 intel_engine_cs change
> - some sparse fixes from Changbin
>
> ----------------------------------------------------------------
> Chris Wilson (10):
> drm/i915/gvt: Add runtime pm around fences
> drm/i915/gvt: i915_gem_object_create() returns an error pointer
> drm/i915/gvt: Use the returned VMA to provide the virtual address
> drm/i915/gvt: Remove dangerous unpin of backing storage of bound GPU object
> drm/i915/gvt: Hold a reference on the request
> drm/i915/gvt: Stop checking for impossible interrupts from a kthread
> drm/i915/gvt: Stop waiting whilst holding struct_mutex
> drm/i915/gvt: Use common mapping routines for indirect_ctx object
> drm/i915/gvt: Use common mapping routines for shadow_bb object
> drm/i915/gvt: Remove defunct vmap_batch()
>
> Du, Changbin (4):
> drm/i915/gvt: fix sparse warnings on different address spaces
> drm/i915/gvt: mark symbols static where possible
> drm/i915/gvt: fix spare warnings on odd constant _Bool cast
> drm/i915/gvt: do not ignore return value of create_scratch_page
>
> Zhenyu Wang (5):
> drm/i915/gvt: clean up intel_gvt.h as interface for i915 core
> MAINTAINERS: Add new Intel GVT-g driver maintainer
> drm/i915/gvt: Fix warning on obsolete function usage
> Documentation/gpu: Add section for Intel GVT-g host support
> drm/i915/gvt: properly access enabled intel_engine_cs
>
> Documentation/gpu/i915.rst | 9 +++
> MAINTAINERS | 10 +++
> drivers/gpu/drm/i915/gvt/aperture_gm.c | 11 +++
> drivers/gpu/drm/i915/gvt/cfg_space.c | 1 +
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 135 +++++++++++---------------------
> drivers/gpu/drm/i915/gvt/display.c | 3 +-
> drivers/gpu/drm/i915/gvt/edid.c | 1 +
> drivers/gpu/drm/i915/gvt/execlist.c | 48 +++++++-----
> drivers/gpu/drm/i915/gvt/firmware.c | 10 ++-
> drivers/gpu/drm/i915/gvt/gtt.c | 15 ++--
> drivers/gpu/drm/i915/gvt/gvt.c | 19 +++--
> drivers/gpu/drm/i915/gvt/gvt.h | 9 ++-
> drivers/gpu/drm/i915/gvt/handlers.c | 13 +--
> drivers/gpu/drm/i915/gvt/interrupt.c | 3 +-
> drivers/gpu/drm/i915/gvt/mmio.c | 1 +
> drivers/gpu/drm/i915/gvt/opregion.c | 3 +-
> drivers/gpu/drm/i915/gvt/render.c | 1 +
> drivers/gpu/drm/i915/gvt/sched_policy.c | 15 ++--
> drivers/gpu/drm/i915/gvt/scheduler.c | 62 ++++++++-------
> drivers/gpu/drm/i915/gvt/vgpu.c | 2 +
> drivers/gpu/drm/i915/i915_drv.h | 4 +-
> drivers/gpu/drm/i915/intel_gvt.c | 8 +-
> drivers/gpu/drm/i915/intel_gvt.h | 3 +-
> 23 files changed, 208 insertions(+), 178 deletions(-)
>
>
> --
> Open Source Technology Center, Intel ltd.
>
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-10-20 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 10:13 [PULL] GVT-g device model core fixes Zhenyu Wang
2016-10-20 13:30 ` Daniel Vetter [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=20161020133045.GU20761@phenom.ffwll.local \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox