lkml.org 
[lkml]   [2020]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[V3 0/3] Fixed dump_backtrace() when task running on another cpu
Date
We cannot get FP and PC when the task is running on another CPU,
task->thread.cpu_context is the last time the task was switched out,
it's better to give a reminder than to provide wrong information
for example when Task blocked in spinlock/interrupt/busy loop.

The task_running() should be renamed to task_running_on_rq()
like the naming of task_running_on_cpu(), this is what it
originally mean.

Add task_running() no rq required.

V2:
- Add task_running_oncpu()
v3:
- Renamed task_running() to task_running_on_rq()
- Renamed task_running_oncpu() to task_running()

Wang Qing (3):
ARM64:fixed dump_backtrace() when task running on another cpu
sched:add task_running()
sched:rename task_running() and to task_running_on_rq

arch/arm64/kernel/traps.c | 7 +++++++
include/linux/sched.h | 10 ++++++++++
kernel/sched/core.c | 14 +++++++-------
kernel/sched/deadline.c | 6 +++---
kernel/sched/fair.c | 2 +-
kernel/sched/rt.c | 6 +++---
kernel/sched/sched.h | 2 +-
7 files changed, 32 insertions(+), 15 deletions(-)

--
2.7.4

\
 
 \ /
  Last update: 2020-04-14 14:37    [W:0.760 / U:0.148 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site