Commit 954180aa authored by Zhenyu Wang's avatar Zhenyu Wang

drm/i915/gvt: remove some debug messages in scheduler timer handler

As those debug messages might appear in every timer call for scheduler,
it's too noisy, eat too much log and aren't meaningful. So remove them.

Cc: Ping Gao <ping.a.gao@intel.com>
Signed-off-by: default avatarZhenyu Wang <zhenyuw@linux.intel.com>
parent efa69d73
...@@ -133,9 +133,6 @@ static void try_to_schedule_next_vgpu(struct intel_gvt *gvt) ...@@ -133,9 +133,6 @@ static void try_to_schedule_next_vgpu(struct intel_gvt *gvt)
if (!scheduler->next_vgpu) if (!scheduler->next_vgpu)
return; return;
gvt_dbg_sched("try to schedule next vgpu %d\n",
scheduler->next_vgpu->id);
/* /*
* after the flag is set, workload dispatch thread will * after the flag is set, workload dispatch thread will
* stop dispatching workload for current vgpu * stop dispatching workload for current vgpu
...@@ -144,10 +141,8 @@ static void try_to_schedule_next_vgpu(struct intel_gvt *gvt) ...@@ -144,10 +141,8 @@ static void try_to_schedule_next_vgpu(struct intel_gvt *gvt)
/* still have uncompleted workload? */ /* still have uncompleted workload? */
for_each_engine(engine, gvt->dev_priv, i) { for_each_engine(engine, gvt->dev_priv, i) {
if (scheduler->current_workload[i]) { if (scheduler->current_workload[i])
gvt_dbg_sched("still have running workload\n");
return; return;
}
} }
cur_time = ktime_get(); cur_time = ktime_get();
......
...@@ -274,11 +274,8 @@ static struct intel_vgpu_workload *pick_next_workload( ...@@ -274,11 +274,8 @@ static struct intel_vgpu_workload *pick_next_workload(
goto out; goto out;
} }
if (list_empty(workload_q_head(scheduler->current_vgpu, ring_id))) { if (list_empty(workload_q_head(scheduler->current_vgpu, ring_id)))
gvt_dbg_sched("ring id %d stop - no available workload\n",
ring_id);
goto out; goto out;
}
/* /*
* still have current workload, maybe the workload disptacher * still have current workload, maybe the workload disptacher
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment