2014-01-27 12:42:01 +08:00
|
|
|
/*
|
|
|
|
* Generic entry point for the idle threads
|
|
|
|
*/
|
|
|
|
#include <linux/sched.h>
|
2017-02-01 23:36:40 +08:00
|
|
|
#include <linux/sched/idle.h>
|
2014-01-27 12:42:01 +08:00
|
|
|
#include <linux/cpu.h>
|
|
|
|
#include <linux/cpuidle.h>
|
2016-02-27 02:43:41 +08:00
|
|
|
#include <linux/cpuhotplug.h>
|
2014-01-27 12:42:01 +08:00
|
|
|
#include <linux/tick.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/stackprotector.h>
|
2015-02-13 06:33:15 +08:00
|
|
|
#include <linux/suspend.h>
|
livepatch: change to a per-task consistency model
Change livepatch to use a basic per-task consistency model. This is the
foundation which will eventually enable us to patch those ~10% of
security patches which change function or data semantics. This is the
biggest remaining piece needed to make livepatch more generally useful.
This code stems from the design proposal made by Vojtech [1] in November
2014. It's a hybrid of kGraft and kpatch: it uses kGraft's per-task
consistency and syscall barrier switching combined with kpatch's stack
trace switching. There are also a number of fallback options which make
it quite flexible.
Patches are applied on a per-task basis, when the task is deemed safe to
switch over. When a patch is enabled, livepatch enters into a
transition state where tasks are converging to the patched state.
Usually this transition state can complete in a few seconds. The same
sequence occurs when a patch is disabled, except the tasks converge from
the patched state to the unpatched state.
An interrupt handler inherits the patched state of the task it
interrupts. The same is true for forked tasks: the child inherits the
patched state of the parent.
Livepatch uses several complementary approaches to determine when it's
safe to patch tasks:
1. The first and most effective approach is stack checking of sleeping
tasks. If no affected functions are on the stack of a given task,
the task is patched. In most cases this will patch most or all of
the tasks on the first try. Otherwise it'll keep trying
periodically. This option is only available if the architecture has
reliable stacks (HAVE_RELIABLE_STACKTRACE).
2. The second approach, if needed, is kernel exit switching. A
task is switched when it returns to user space from a system call, a
user space IRQ, or a signal. It's useful in the following cases:
a) Patching I/O-bound user tasks which are sleeping on an affected
function. In this case you have to send SIGSTOP and SIGCONT to
force it to exit the kernel and be patched.
b) Patching CPU-bound user tasks. If the task is highly CPU-bound
then it will get patched the next time it gets interrupted by an
IRQ.
c) In the future it could be useful for applying patches for
architectures which don't yet have HAVE_RELIABLE_STACKTRACE. In
this case you would have to signal most of the tasks on the
system. However this isn't supported yet because there's
currently no way to patch kthreads without
HAVE_RELIABLE_STACKTRACE.
3. For idle "swapper" tasks, since they don't ever exit the kernel, they
instead have a klp_update_patch_state() call in the idle loop which
allows them to be patched before the CPU enters the idle state.
(Note there's not yet such an approach for kthreads.)
All the above approaches may be skipped by setting the 'immediate' flag
in the 'klp_patch' struct, which will disable per-task consistency and
patch all tasks immediately. This can be useful if the patch doesn't
change any function or data semantics. Note that, even with this flag
set, it's possible that some tasks may still be running with an old
version of the function, until that function returns.
There's also an 'immediate' flag in the 'klp_func' struct which allows
you to specify that certain functions in the patch can be applied
without per-task consistency. This might be useful if you want to patch
a common function like schedule(), and the function change doesn't need
consistency but the rest of the patch does.
For architectures which don't have HAVE_RELIABLE_STACKTRACE, the user
must set patch->immediate which causes all tasks to be patched
immediately. This option should be used with care, only when the patch
doesn't change any function or data semantics.
In the future, architectures which don't have HAVE_RELIABLE_STACKTRACE
may be allowed to use per-task consistency if we can come up with
another way to patch kthreads.
The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
is in transition. Only a single patch (the topmost patch on the stack)
can be in transition at a given time. A patch can remain in transition
indefinitely, if any of the tasks are stuck in the initial patch state.
A transition can be reversed and effectively canceled by writing the
opposite value to the /sys/kernel/livepatch/<patch>/enabled file while
the transition is in progress. Then all the tasks will attempt to
converge back to the original patch state.
[1] https://lkml.kernel.org/r/20141107140458.GA21774@suse.cz
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Acked-by: Miroslav Benes <mbenes@suse.cz>
Acked-by: Ingo Molnar <mingo@kernel.org> # for the scheduler changes
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2017-02-14 09:42:40 +08:00
|
|
|
#include <linux/livepatch.h>
|
2014-01-27 12:42:01 +08:00
|
|
|
|
|
|
|
#include <asm/tlb.h>
|
|
|
|
|
|
|
|
#include <trace/events/power.h>
|
|
|
|
|
2014-06-05 01:31:18 +08:00
|
|
|
#include "sched.h"
|
|
|
|
|
2016-10-08 08:02:55 +08:00
|
|
|
/* Linker adds these: start and end of __cpuidle functions */
|
|
|
|
extern char __cpuidle_text_start[], __cpuidle_text_end[];
|
|
|
|
|
2015-05-10 07:18:03 +08:00
|
|
|
/**
|
|
|
|
* sched_idle_set_state - Record idle state for the current CPU.
|
|
|
|
* @idle_state: State to record.
|
|
|
|
*/
|
|
|
|
void sched_idle_set_state(struct cpuidle_state *idle_state)
|
|
|
|
{
|
|
|
|
idle_set_state(this_rq(), idle_state);
|
|
|
|
}
|
|
|
|
|
2014-01-27 12:42:01 +08:00
|
|
|
static int __read_mostly cpu_idle_force_poll;
|
|
|
|
|
|
|
|
void cpu_idle_poll_ctrl(bool enable)
|
|
|
|
{
|
|
|
|
if (enable) {
|
|
|
|
cpu_idle_force_poll++;
|
|
|
|
} else {
|
|
|
|
cpu_idle_force_poll--;
|
|
|
|
WARN_ON_ONCE(cpu_idle_force_poll < 0);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
#ifdef CONFIG_GENERIC_IDLE_POLL_SETUP
|
|
|
|
static int __init cpu_idle_poll_setup(char *__unused)
|
|
|
|
{
|
|
|
|
cpu_idle_force_poll = 1;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
__setup("nohlt", cpu_idle_poll_setup);
|
|
|
|
|
|
|
|
static int __init cpu_idle_nopoll_setup(char *__unused)
|
|
|
|
{
|
|
|
|
cpu_idle_force_poll = 0;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
__setup("hlt", cpu_idle_nopoll_setup);
|
|
|
|
#endif
|
|
|
|
|
2016-10-08 08:02:55 +08:00
|
|
|
static noinline int __cpuidle cpu_idle_poll(void)
|
2014-01-27 12:42:01 +08:00
|
|
|
{
|
|
|
|
rcu_idle_enter();
|
|
|
|
trace_cpu_idle_rcuidle(0, smp_processor_id());
|
|
|
|
local_irq_enable();
|
2015-10-09 02:36:06 +08:00
|
|
|
stop_critical_timings();
|
2015-01-21 18:57:25 +08:00
|
|
|
while (!tif_need_resched() &&
|
|
|
|
(cpu_idle_force_poll || tick_check_broadcast_expired()))
|
2014-01-27 12:42:01 +08:00
|
|
|
cpu_relax();
|
2015-10-09 02:36:06 +08:00
|
|
|
start_critical_timings();
|
2014-01-27 12:42:01 +08:00
|
|
|
trace_cpu_idle_rcuidle(PWR_EVENT_EXIT, smp_processor_id());
|
|
|
|
rcu_idle_exit();
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Weak implementations for optional arch specific functions */
|
|
|
|
void __weak arch_cpu_idle_prepare(void) { }
|
|
|
|
void __weak arch_cpu_idle_enter(void) { }
|
|
|
|
void __weak arch_cpu_idle_exit(void) { }
|
|
|
|
void __weak arch_cpu_idle_dead(void) { }
|
|
|
|
void __weak arch_cpu_idle(void)
|
|
|
|
{
|
|
|
|
cpu_idle_force_poll = 1;
|
|
|
|
local_irq_enable();
|
|
|
|
}
|
|
|
|
|
2015-05-10 07:18:46 +08:00
|
|
|
/**
|
|
|
|
* default_idle_call - Default CPU idle routine.
|
|
|
|
*
|
|
|
|
* To use when the cpuidle framework cannot be used.
|
|
|
|
*/
|
2016-10-08 08:02:55 +08:00
|
|
|
void __cpuidle default_idle_call(void)
|
2015-05-05 04:53:22 +08:00
|
|
|
{
|
2015-07-21 00:34:50 +08:00
|
|
|
if (current_clr_polling_and_test()) {
|
2015-05-05 04:53:22 +08:00
|
|
|
local_irq_enable();
|
2015-07-21 00:34:50 +08:00
|
|
|
} else {
|
|
|
|
stop_critical_timings();
|
2015-05-05 04:53:22 +08:00
|
|
|
arch_cpu_idle();
|
2015-07-21 00:34:50 +08:00
|
|
|
start_critical_timings();
|
|
|
|
}
|
2015-05-05 04:53:22 +08:00
|
|
|
}
|
|
|
|
|
2015-05-05 04:53:35 +08:00
|
|
|
static int call_cpuidle(struct cpuidle_driver *drv, struct cpuidle_device *dev,
|
|
|
|
int next_state)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* The idle task must be scheduled, it is pointless to go to idle, just
|
|
|
|
* update no idle residency and return.
|
|
|
|
*/
|
|
|
|
if (current_clr_polling_and_test()) {
|
|
|
|
dev->last_residency = 0;
|
|
|
|
local_irq_enable();
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Enter the idle state previously returned by the governor decision.
|
|
|
|
* This function will block until an interrupt occurs and will take
|
|
|
|
* care of re-enabling the local interrupts
|
|
|
|
*/
|
2015-05-10 07:18:46 +08:00
|
|
|
return cpuidle_enter(drv, dev, next_state);
|
2015-05-05 04:53:35 +08:00
|
|
|
}
|
|
|
|
|
2014-03-03 15:48:51 +08:00
|
|
|
/**
|
|
|
|
* cpuidle_idle_call - the main idle function
|
|
|
|
*
|
|
|
|
* NOTE: no locks or semaphores should be used here
|
2014-06-05 01:31:16 +08:00
|
|
|
*
|
|
|
|
* On archs that support TIF_POLLING_NRFLAG, is called with polling
|
|
|
|
* set, and it returns with polling set. If it ever stops polling, it
|
|
|
|
* must clear the polling bit.
|
2014-03-03 15:48:51 +08:00
|
|
|
*/
|
2014-04-21 07:26:58 +08:00
|
|
|
static void cpuidle_idle_call(void)
|
2014-03-03 15:48:51 +08:00
|
|
|
{
|
2016-06-02 01:52:16 +08:00
|
|
|
struct cpuidle_device *dev = cpuidle_get_device();
|
2014-03-03 15:48:51 +08:00
|
|
|
struct cpuidle_driver *drv = cpuidle_get_cpu_driver(dev);
|
2014-04-11 19:55:48 +08:00
|
|
|
int next_state, entered_state;
|
2014-03-03 15:48:51 +08:00
|
|
|
|
2014-03-03 15:48:54 +08:00
|
|
|
/*
|
|
|
|
* Check if the idle task must be rescheduled. If it is the
|
2014-04-11 19:47:16 +08:00
|
|
|
* case, exit the function after re-enabling the local irq.
|
2014-03-03 15:48:54 +08:00
|
|
|
*/
|
2014-04-11 19:47:16 +08:00
|
|
|
if (need_resched()) {
|
2014-03-03 15:48:53 +08:00
|
|
|
local_irq_enable();
|
2014-04-21 07:26:58 +08:00
|
|
|
return;
|
2014-03-03 15:48:53 +08:00
|
|
|
}
|
|
|
|
|
2014-03-03 15:48:54 +08:00
|
|
|
/*
|
|
|
|
* Tell the RCU framework we are entering an idle section,
|
|
|
|
* so no more rcu read side critical sections and one more
|
|
|
|
* step to the grace period
|
|
|
|
*/
|
2014-03-03 15:48:52 +08:00
|
|
|
rcu_idle_enter();
|
|
|
|
|
2015-05-05 04:53:22 +08:00
|
|
|
if (cpuidle_not_available(drv, dev)) {
|
|
|
|
default_idle_call();
|
|
|
|
goto exit_idle;
|
|
|
|
}
|
2015-03-03 05:26:55 +08:00
|
|
|
|
2015-02-13 06:33:15 +08:00
|
|
|
/*
|
|
|
|
* Suspend-to-idle ("freeze") is a system state in which all user space
|
|
|
|
* has been frozen, all I/O devices have been suspended and the only
|
|
|
|
* activity happens here and in iterrupts (if any). In that case bypass
|
|
|
|
* the cpuidle governor and go stratight for the deepest idle state
|
|
|
|
* available. Possibly also suspend the local tick and the entire
|
|
|
|
* timekeeping to prevent timer interrupts from kicking us out of idle
|
|
|
|
* until a proper wakeup interrupt happens.
|
|
|
|
*/
|
2016-11-29 15:03:04 +08:00
|
|
|
|
|
|
|
if (idle_should_freeze() || dev->use_deepest_state) {
|
|
|
|
if (idle_should_freeze()) {
|
|
|
|
entered_state = cpuidle_enter_freeze(drv, dev);
|
|
|
|
if (entered_state > 0) {
|
|
|
|
local_irq_enable();
|
|
|
|
goto exit_idle;
|
|
|
|
}
|
2015-03-03 05:26:55 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
next_state = cpuidle_find_deepest_state(drv, dev);
|
2015-05-05 04:53:35 +08:00
|
|
|
call_cpuidle(drv, dev, next_state);
|
2015-03-03 05:26:55 +08:00
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* Ask the cpuidle framework to choose a convenient idle state.
|
|
|
|
*/
|
|
|
|
next_state = cpuidle_select(drv, dev);
|
2015-05-05 04:53:35 +08:00
|
|
|
entered_state = call_cpuidle(drv, dev, next_state);
|
|
|
|
/*
|
|
|
|
* Give the governor an opportunity to reflect on the outcome
|
|
|
|
*/
|
2015-03-03 05:26:55 +08:00
|
|
|
cpuidle_reflect(dev, entered_state);
|
2015-05-05 04:53:35 +08:00
|
|
|
}
|
2014-04-11 19:55:48 +08:00
|
|
|
|
|
|
|
exit_idle:
|
2014-03-03 15:48:53 +08:00
|
|
|
__current_set_polling();
|
2014-03-03 15:48:51 +08:00
|
|
|
|
2014-03-03 15:48:54 +08:00
|
|
|
/*
|
2014-04-11 19:55:48 +08:00
|
|
|
* It is up to the idle functions to reenable local interrupts
|
2014-03-03 15:48:54 +08:00
|
|
|
*/
|
2014-03-03 15:48:52 +08:00
|
|
|
if (WARN_ON_ONCE(irqs_disabled()))
|
|
|
|
local_irq_enable();
|
|
|
|
|
|
|
|
rcu_idle_exit();
|
2014-03-03 15:48:51 +08:00
|
|
|
}
|
|
|
|
|
2014-01-27 12:42:01 +08:00
|
|
|
/*
|
|
|
|
* Generic idle loop implementation
|
2014-06-05 01:31:16 +08:00
|
|
|
*
|
|
|
|
* Called with polling cleared.
|
2014-01-27 12:42:01 +08:00
|
|
|
*/
|
2016-11-29 15:03:05 +08:00
|
|
|
static void do_idle(void)
|
2014-01-27 12:42:01 +08:00
|
|
|
{
|
2016-11-29 15:03:05 +08:00
|
|
|
/*
|
|
|
|
* If the arch has a polling bit, we maintain an invariant:
|
|
|
|
*
|
|
|
|
* Our polling bit is clear if we're not scheduled (i.e. if rq->curr !=
|
|
|
|
* rq->idle). This means that, if rq->idle has the polling bit set,
|
|
|
|
* then setting need_resched is guaranteed to cause the CPU to
|
|
|
|
* reschedule.
|
|
|
|
*/
|
2014-01-27 12:42:01 +08:00
|
|
|
|
2016-11-29 15:03:05 +08:00
|
|
|
__current_set_polling();
|
2017-06-07 10:49:02 +08:00
|
|
|
quiet_vmstat();
|
2016-11-29 15:03:05 +08:00
|
|
|
tick_nohz_idle_enter();
|
2014-01-27 12:42:01 +08:00
|
|
|
|
2016-11-29 15:03:05 +08:00
|
|
|
while (!need_resched()) {
|
|
|
|
check_pgt_cache();
|
|
|
|
rmb();
|
2014-01-27 12:42:01 +08:00
|
|
|
|
2016-11-29 15:03:05 +08:00
|
|
|
if (cpu_is_offline(smp_processor_id())) {
|
|
|
|
cpuhp_report_idle_dead();
|
|
|
|
arch_cpu_idle_dead();
|
2014-01-27 12:42:01 +08:00
|
|
|
}
|
2014-02-25 01:22:07 +08:00
|
|
|
|
2016-11-29 15:03:05 +08:00
|
|
|
local_irq_disable();
|
|
|
|
arch_cpu_idle_enter();
|
2014-06-05 01:31:16 +08:00
|
|
|
|
|
|
|
/*
|
2016-11-29 15:03:05 +08:00
|
|
|
* In poll mode we reenable interrupts and spin. Also if we
|
|
|
|
* detected in the wakeup from idle path that the tick
|
|
|
|
* broadcast device expired for us, we don't want to go deep
|
|
|
|
* idle as we know that the IPI is going to arrive right away.
|
2014-06-05 01:31:16 +08:00
|
|
|
*/
|
2016-11-29 15:03:05 +08:00
|
|
|
if (cpu_idle_force_poll || tick_check_broadcast_expired())
|
|
|
|
cpu_idle_poll();
|
|
|
|
else
|
|
|
|
cpuidle_idle_call();
|
|
|
|
arch_cpu_idle_exit();
|
2014-01-27 12:42:01 +08:00
|
|
|
}
|
2016-11-29 15:03:05 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Since we fell out of the loop above, we know TIF_NEED_RESCHED must
|
|
|
|
* be set, propagate it into PREEMPT_NEED_RESCHED.
|
|
|
|
*
|
|
|
|
* This is required because for polling idle loops we will not have had
|
|
|
|
* an IPI to fold the state for us.
|
|
|
|
*/
|
|
|
|
preempt_set_need_resched();
|
|
|
|
tick_nohz_idle_exit();
|
|
|
|
__current_clr_polling();
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We promise to call sched_ttwu_pending() and reschedule if
|
|
|
|
* need_resched() is set while polling is set. That means that clearing
|
|
|
|
* polling needs to be visible before doing these things.
|
|
|
|
*/
|
|
|
|
smp_mb__after_atomic();
|
|
|
|
|
|
|
|
sched_ttwu_pending();
|
sched/core: Call __schedule() from do_idle() without enabling preemption
I finally got around to creating trampolines for dynamically allocated
ftrace_ops with using synchronize_rcu_tasks(). For users of the ftrace
function hook callbacks, like perf, that allocate the ftrace_ops
descriptor via kmalloc() and friends, ftrace was not able to optimize
the functions being traced to use a trampoline because they would also
need to be allocated dynamically. The problem is that they cannot be
freed when CONFIG_PREEMPT is set, as there's no way to tell if a task
was preempted on the trampoline. That was before Paul McKenney
implemented synchronize_rcu_tasks() that would make sure all tasks
(except idle) have scheduled out or have entered user space.
While testing this, I triggered this bug:
BUG: unable to handle kernel paging request at ffffffffa0230077
...
RIP: 0010:0xffffffffa0230077
...
Call Trace:
schedule+0x5/0xe0
schedule_preempt_disabled+0x18/0x30
do_idle+0x172/0x220
What happened was that the idle task was preempted on the trampoline.
As synchronize_rcu_tasks() ignores the idle thread, there's nothing
that lets ftrace know that the idle task was preempted on a trampoline.
The idle task shouldn't need to ever enable preemption. The idle task
is simply a loop that calls schedule or places the cpu into idle mode.
In fact, having preemption enabled is inefficient, because it can
happen when idle is just about to call schedule anyway, which would
cause schedule to be called twice. Once for when the interrupt came in
and was returning back to normal context, and then again in the normal
path that the idle loop is running in, which would be pointless, as it
had already scheduled.
The only reason schedule_preempt_disable() enables preemption is to be
able to call sched_submit_work(), which requires preemption enabled. As
this is a nop when the task is in the RUNNING state, and idle is always
in the running state, there's no reason that idle needs to enable
preemption. But that means it cannot use schedule_preempt_disable() as
other callers of that function require calling sched_submit_work().
Adding a new function local to kernel/sched/ that allows idle to call
the scheduler without enabling preemption, fixes the
synchronize_rcu_tasks() issue, as well as removes the pointless spurious
schedule calls caused by interrupts happening in the brief window where
preemption is enabled just before it calls schedule.
Reviewed: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/20170414084809.3dacde2a@gandalf.local.home
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2017-04-14 20:48:09 +08:00
|
|
|
schedule_idle();
|
livepatch: change to a per-task consistency model
Change livepatch to use a basic per-task consistency model. This is the
foundation which will eventually enable us to patch those ~10% of
security patches which change function or data semantics. This is the
biggest remaining piece needed to make livepatch more generally useful.
This code stems from the design proposal made by Vojtech [1] in November
2014. It's a hybrid of kGraft and kpatch: it uses kGraft's per-task
consistency and syscall barrier switching combined with kpatch's stack
trace switching. There are also a number of fallback options which make
it quite flexible.
Patches are applied on a per-task basis, when the task is deemed safe to
switch over. When a patch is enabled, livepatch enters into a
transition state where tasks are converging to the patched state.
Usually this transition state can complete in a few seconds. The same
sequence occurs when a patch is disabled, except the tasks converge from
the patched state to the unpatched state.
An interrupt handler inherits the patched state of the task it
interrupts. The same is true for forked tasks: the child inherits the
patched state of the parent.
Livepatch uses several complementary approaches to determine when it's
safe to patch tasks:
1. The first and most effective approach is stack checking of sleeping
tasks. If no affected functions are on the stack of a given task,
the task is patched. In most cases this will patch most or all of
the tasks on the first try. Otherwise it'll keep trying
periodically. This option is only available if the architecture has
reliable stacks (HAVE_RELIABLE_STACKTRACE).
2. The second approach, if needed, is kernel exit switching. A
task is switched when it returns to user space from a system call, a
user space IRQ, or a signal. It's useful in the following cases:
a) Patching I/O-bound user tasks which are sleeping on an affected
function. In this case you have to send SIGSTOP and SIGCONT to
force it to exit the kernel and be patched.
b) Patching CPU-bound user tasks. If the task is highly CPU-bound
then it will get patched the next time it gets interrupted by an
IRQ.
c) In the future it could be useful for applying patches for
architectures which don't yet have HAVE_RELIABLE_STACKTRACE. In
this case you would have to signal most of the tasks on the
system. However this isn't supported yet because there's
currently no way to patch kthreads without
HAVE_RELIABLE_STACKTRACE.
3. For idle "swapper" tasks, since they don't ever exit the kernel, they
instead have a klp_update_patch_state() call in the idle loop which
allows them to be patched before the CPU enters the idle state.
(Note there's not yet such an approach for kthreads.)
All the above approaches may be skipped by setting the 'immediate' flag
in the 'klp_patch' struct, which will disable per-task consistency and
patch all tasks immediately. This can be useful if the patch doesn't
change any function or data semantics. Note that, even with this flag
set, it's possible that some tasks may still be running with an old
version of the function, until that function returns.
There's also an 'immediate' flag in the 'klp_func' struct which allows
you to specify that certain functions in the patch can be applied
without per-task consistency. This might be useful if you want to patch
a common function like schedule(), and the function change doesn't need
consistency but the rest of the patch does.
For architectures which don't have HAVE_RELIABLE_STACKTRACE, the user
must set patch->immediate which causes all tasks to be patched
immediately. This option should be used with care, only when the patch
doesn't change any function or data semantics.
In the future, architectures which don't have HAVE_RELIABLE_STACKTRACE
may be allowed to use per-task consistency if we can come up with
another way to patch kthreads.
The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
is in transition. Only a single patch (the topmost patch on the stack)
can be in transition at a given time. A patch can remain in transition
indefinitely, if any of the tasks are stuck in the initial patch state.
A transition can be reversed and effectively canceled by writing the
opposite value to the /sys/kernel/livepatch/<patch>/enabled file while
the transition is in progress. Then all the tasks will attempt to
converge back to the original patch state.
[1] https://lkml.kernel.org/r/20141107140458.GA21774@suse.cz
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Acked-by: Miroslav Benes <mbenes@suse.cz>
Acked-by: Ingo Molnar <mingo@kernel.org> # for the scheduler changes
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2017-02-14 09:42:40 +08:00
|
|
|
|
|
|
|
if (unlikely(klp_patch_pending(current)))
|
|
|
|
klp_update_patch_state(current);
|
2014-01-27 12:42:01 +08:00
|
|
|
}
|
|
|
|
|
2016-10-08 08:02:55 +08:00
|
|
|
bool cpu_in_idle(unsigned long pc)
|
|
|
|
{
|
|
|
|
return pc >= (unsigned long)__cpuidle_text_start &&
|
|
|
|
pc < (unsigned long)__cpuidle_text_end;
|
|
|
|
}
|
|
|
|
|
2016-11-29 15:03:05 +08:00
|
|
|
struct idle_timer {
|
|
|
|
struct hrtimer timer;
|
|
|
|
int done;
|
|
|
|
};
|
|
|
|
|
|
|
|
static enum hrtimer_restart idle_inject_timer_fn(struct hrtimer *timer)
|
|
|
|
{
|
|
|
|
struct idle_timer *it = container_of(timer, struct idle_timer, timer);
|
|
|
|
|
|
|
|
WRITE_ONCE(it->done, 1);
|
|
|
|
set_tsk_need_resched(current);
|
|
|
|
|
|
|
|
return HRTIMER_NORESTART;
|
|
|
|
}
|
|
|
|
|
|
|
|
void play_idle(unsigned long duration_ms)
|
|
|
|
{
|
|
|
|
struct idle_timer it;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Only FIFO tasks can disable the tick since they don't need the forced
|
|
|
|
* preemption.
|
|
|
|
*/
|
|
|
|
WARN_ON_ONCE(current->policy != SCHED_FIFO);
|
|
|
|
WARN_ON_ONCE(current->nr_cpus_allowed != 1);
|
|
|
|
WARN_ON_ONCE(!(current->flags & PF_KTHREAD));
|
|
|
|
WARN_ON_ONCE(!(current->flags & PF_NO_SETAFFINITY));
|
|
|
|
WARN_ON_ONCE(!duration_ms);
|
|
|
|
|
|
|
|
rcu_sleep_check();
|
|
|
|
preempt_disable();
|
|
|
|
current->flags |= PF_IDLE;
|
|
|
|
cpuidle_use_deepest_state(true);
|
|
|
|
|
|
|
|
it.done = 0;
|
|
|
|
hrtimer_init_on_stack(&it.timer, CLOCK_MONOTONIC, HRTIMER_MODE_REL);
|
|
|
|
it.timer.function = idle_inject_timer_fn;
|
|
|
|
hrtimer_start(&it.timer, ms_to_ktime(duration_ms), HRTIMER_MODE_REL_PINNED);
|
|
|
|
|
|
|
|
while (!READ_ONCE(it.done))
|
|
|
|
do_idle();
|
|
|
|
|
|
|
|
cpuidle_use_deepest_state(false);
|
|
|
|
current->flags &= ~PF_IDLE;
|
|
|
|
|
|
|
|
preempt_fold_need_resched();
|
|
|
|
preempt_enable();
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(play_idle);
|
|
|
|
|
2014-01-27 12:42:01 +08:00
|
|
|
void cpu_startup_entry(enum cpuhp_state state)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* This #ifdef needs to die, but it's too late in the cycle to
|
|
|
|
* make this generic (arm and sh have never invoked the canary
|
|
|
|
* init for the non boot cpus!). Will be fixed in 3.11
|
|
|
|
*/
|
|
|
|
#ifdef CONFIG_X86
|
|
|
|
/*
|
|
|
|
* If we're the non-boot CPU, nothing set the stack canary up
|
|
|
|
* for us. The boot CPU already has it initialized but no harm
|
|
|
|
* in doing it again. This is a good place for updating it, as
|
|
|
|
* we wont ever return from this function (so the invalid
|
|
|
|
* canaries already on the stack wont ever trigger).
|
|
|
|
*/
|
|
|
|
boot_init_stack_canary();
|
|
|
|
#endif
|
|
|
|
arch_cpu_idle_prepare();
|
2016-02-27 02:43:41 +08:00
|
|
|
cpuhp_online_idle(state);
|
2016-11-29 15:03:05 +08:00
|
|
|
while (1)
|
|
|
|
do_idle();
|
2014-01-27 12:42:01 +08:00
|
|
|
}
|