> > > Since intel_gvt_init() is called at early initialization stage and
> > > require the status notifier head has been initiated, I initiate it in
> > > intel_engine_setup().
> > >
> > > v2: remove a redundant newline. (chris)
> > >
> > > Signed-off-by: Changbin Du
> > > Reviewed-by: Chris Wil
On Mon, Mar 13, 2017 at 12:03:30PM +0800, Zhenyu Wang wrote:
> On 2017.03.13 10:47:11 +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,
> >
On 2017.03.13 10:47:11 +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 to improve
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
