trace/sched: set priority to 150 for deadline tasks

As deadline tasks doesn't have priority, their priority is set
to -1. If there are any deadline tasks in the system, chrome/tracing
doesn't show results as expected as it can't recognize tasks with
priority -1. Fix it by using 150 as priority for deadline tasks.

Change-Id: I49b43f77b97ebfe6d79a7c9e9ec346ea60e79768
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
This commit is contained in:
Satya Durga Srinivasu Prabhala
2019-03-07 22:22:49 -08:00
parent 4000d38b35
commit 779fe47fd2

View File

@ -205,11 +205,11 @@ TRACE_EVENT(sched_switch,
TP_fast_assign(
memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
__entry->prev_pid = prev->pid;
__entry->prev_prio = prev->prio;
__entry->prev_prio = prev->prio == -1 ? 150 : prev->prio;
__entry->prev_state = __trace_sched_switch_state(preempt, prev);
memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
__entry->next_pid = next->pid;
__entry->next_prio = next->prio;
__entry->next_prio = next->prio == -1 ? 150 : next->prio;
/* XXX SCHED_DEADLINE */
),