[Intel-gfx] [PATCH] drm/i915: make context status notifier head be per engine

2017-03-21 Thread Chris Wilson
From: Changbin Du GVTg has introduced the context status notifier to schedule the GVTg workload. At that time, the notifier is bound to GVTg context only, so GVTg is not aware of host workloads. Now we are going to improve GVTg's guest workload scheduler policy, and add Guc emulation support for

Re: [Intel-gfx] [PATCH] drm/i915: make context status notifier head be per engine

2017-03-12 Thread Du, Changbin
hi, chris, On Fri, Mar 10, 2017 at 05:17:17PM +, Chris Wilson wrote: > On Thu, Mar 09, 2017 at 07:27:24PM +0800, changbin...@intel.com wrote: > > From: Changbin Du > > > > GVTg has introduced the context status notifier to schedule the GVTg > > workload. At that time, the notifier is bound t

Re: [Intel-gfx] [PATCH] drm/i915: make context status notifier head be per engine

2017-03-10 Thread Chris Wilson
On Thu, Mar 09, 2017 at 07:27:24PM +0800, changbin...@intel.com wrote: > From: Changbin Du > > GVTg has introduced the context status notifier to schedule the GVTg > workload. At that time, the notifier is bound to GVTg context only, > so GVTg is not aware of host workloads. > > Now we are going

[Intel-gfx] [PATCH] drm/i915: make context status notifier head be per engine

2017-03-09 Thread changbin . du
From: Changbin Du GVTg has introduced the context status notifier to schedule the GVTg workload. At that time, the notifier is bound to GVTg context only, so GVTg is not aware of host workloads. Now we are going to improve GVTg's guest workload scheduler policy, and add Guc emulation support for