Re: [PATCH v8 00/10] Introduce the implementation of GVT context

From: Chris Wilson <chris@chris-wilson.co.uk>
To: Zhi Wang <zhi.a.wang@intel.com>
Cc: intel-gfx@lists.freedesktop.org, zhiyuan.lv@intel.com
Subject: Re: [PATCH v8 00/10] Introduce the implementation of GVT context
Date: Wed, 8 Jun 2016 17:00:58 +0100	[thread overview]
Message-ID: <20160608160058.GO32344@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1465399828-17082-1-git-send-email-zhi.a.wang@intel.com>

On Wed, Jun 08, 2016 at 11:30:18AM -0400, Zhi Wang wrote:
> Bing Niu (1):
>   drm/i915: Introduce host graphics memory partition for GVT-g
> 
> Zhi Wang (9):
>   drm/i915: Factor out i915_pvinfo.h
>   drm/i915: Use offsetof() to calculate the offset of members in PVINFO
>     page
>   drm/i915: Fold vGPU active check into inner functions
>   drm/i915: gvt: Introduce the basic architecture of GVT-g
>   drm/i915: Make ring buffer size of a LRC context configurable
>   drm/i915: Make addressing mode bits in context descriptor configurable
>   drm/i915: Introduce execlist context status change notification
>   drm/i915: Support LRC context single submission
>   drm/i915: Introduce GVT context creation API

You want to also send a 

for-CI: Enable GVT-g by default

patch when sending these series so that we can run BAT and make sure we
don't regress with the added code. Actually, better would be send to
list with disable by default, but send the series to trybot with the
enabling and add the link here. Then the merged patches will include a
reference to the normal CI config, with a reference to the enabled CI
config available as well.

2 very minor comments, but I just wanted to be sure that there were no
accidental changes outside of GVT-g (hence BAT).
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx