[lkml]   [2015]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 0/9] livepatch: consistency model
On Mon, 9 Feb 2015, Josh Poimboeuf wrote:

> My biggest concerns and questions related to this patch set are:
> 1) To safely examine the task stacks, the transition code locks each task's rq
> struct, which requires using the scheduler's internal rq locking functions.
> It seems to work well, but I'm not sure if there's a cleaner way to safely
> do stack checking without stop_machine().

How about we take a slightly different aproach -- put a probe (or ftrace)
on __switch_to() during a klp transition period, and examine stacktraces
for tasks that are just about to start running from there?

The only tasks that would not be covered by this would be purely CPU-bound
tasks that never schedule. But we are likely in trouble with those anyway,
because odds are that non-rescheduling CPU-bound tasks are also
RT-priority tasks running on isolated CPUs, which we will fail to handle

I think Masami used similar trick in his kpatch-without-stopmachine

Jiri Kosina

 \ /
  Last update: 2015-02-13 11:21    [W:2.896 / U:0.504 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site