Sure. That's a good idea. :) > -----Original Message----- > From: Chris Wilson [mailto:chris@xxxxxxxxxxxxxxxxxx] > Sent: Wednesday, June 08, 2016 7:01 PM > To: Wang, Zhi A <zhi.a.wang@xxxxxxxxx> > Cc: Lv, Zhiyuan <zhiyuan.lv@xxxxxxxxx>; Tian, Kevin <kevin.tian@xxxxxxxxx>; > tvrtko.ursulin@xxxxxxxxxxxxxxx; intel-gfx@xxxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH v8 00/10] Introduce the implementation of GVT context > > 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@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
