From 0ff0804b0d52e034459a80ab27c39965d5ea1e39 Mon Sep 17 00:00:00 2001 From: Tvrtko Ursulin Date: Tue, 14 Aug 2018 10:41:30 +0100 Subject: gem_wsim: Context priority support A new workload command ('P') is added which enables per context dynamic priority control. Signed-off-by: Tvrtko Ursulin Reviewed-by: Chris Wilson --- benchmarks/wsim/README | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'benchmarks/wsim') diff --git a/benchmarks/wsim/README b/benchmarks/wsim/README index 01766d37..fd9bff34 100644 --- a/benchmarks/wsim/README +++ b/benchmarks/wsim/README @@ -3,6 +3,7 @@ Workload descriptor format ctx.engine.duration_us.dependency.wait,... ..[-].[/][...].<0|1>,... +P.. d|p|s|t|q|a.,... f @@ -22,6 +23,7 @@ Additional workload steps are also supported: 'q' - Throttle to n max queue depth. 'f' - Create a sync fence. 'a' - Advance the previously created sync fence. + 'P' - Context priority. Engine ids: RCS, BCS, VCS, VCS1, VCS2, VECS @@ -110,3 +112,19 @@ created at the second step. They are submitted ahead of time while still not runnable. When the second RCS batch completes the standalone fence is signaled which allows the two VCS batches to be executed. Finally we wait until the both VCS batches have completed before starting the (optional) next iteration. + +Context priority +---------------- + + P.1.-1 + 1.RCS.1000.0.0 + P.2.1 + 2.BCS.1000.-2.0 + +Context 1 is marked as low priority (-1) and then a batch buffer is submitted +against it. Context 2 is marked as high priority (1) and then a batch buffer +is submitted against it which depends on the batch from context 1. + +Context priority command is executed at workload runtime and is valid until +overriden by another (optional) same context priority change. Actual driver +ioctls are executed only if the priority level has changed for the context. -- cgit v1.2.3