blob: 7b095de356c5775f22da4cc168293c62c96f6059 [file] [log] [blame]
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +01001/*
2 * Context tracking: Probe on high level context boundaries such as kernel
3 * and userspace. This includes syscalls and exceptions entry/exit.
4 *
5 * This is used by RCU to remove its dependency on the timer tick while a CPU
6 * runs in userspace.
7 *
8 * Started by Frederic Weisbecker:
9 *
10 * Copyright (C) 2012 Red Hat, Inc., Frederic Weisbecker <fweisbec@redhat.com>
11 *
12 * Many thanks to Gilad Ben-Yossef, Paul McKenney, Ingo Molnar, Andrew Morton,
13 * Steven Rostedt, Peter Zijlstra for suggestions and improvements.
14 *
15 */
16
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010017#include <linux/context_tracking.h>
18#include <linux/rcupdate.h>
19#include <linux/sched.h>
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010020#include <linux/hardirq.h>
Frederic Weisbecker6a616712012-12-16 20:00:34 +010021#include <linux/export.h>
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010022
Frederic Weisbecker95a79fd2013-01-07 18:12:14 +010023DEFINE_PER_CPU(struct context_tracking, context_tracking) = {
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010024#ifdef CONFIG_CONTEXT_TRACKING_FORCE
25 .active = true,
26#endif
27};
28
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +010029/**
30 * user_enter - Inform the context tracking that the CPU is going to
31 * enter userspace mode.
32 *
33 * This function must be called right before we switch from the kernel
34 * to userspace, when it's guaranteed the remaining kernel instructions
35 * to execute won't use any RCU read side critical section because this
36 * function sets RCU in extended quiescent state.
37 */
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010038void user_enter(void)
39{
40 unsigned long flags;
41
42 /*
43 * Some contexts may involve an exception occuring in an irq,
44 * leading to that nesting:
45 * rcu_irq_enter() rcu_user_exit() rcu_user_exit() rcu_irq_exit()
46 * This would mess up the dyntick_nesting count though. And rcu_irq_*()
47 * helpers are enough to protect RCU uses inside the exception. So
48 * just return immediately if we detect we are in an IRQ.
49 */
50 if (in_interrupt())
51 return;
52
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +010053 /* Kernel threads aren't supposed to go to userspace */
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010054 WARN_ON_ONCE(!current->mm);
55
56 local_irq_save(flags);
Frederic Weisbeckerd65ec122013-07-11 23:59:33 +020057 if ( __this_cpu_read(context_tracking.state) != IN_USER) {
58 if (__this_cpu_read(context_tracking.active)) {
59 /*
60 * At this stage, only low level arch entry code remains and
61 * then we'll run in userspace. We can assume there won't be
62 * any RCU read-side critical section until the next call to
63 * user_exit() or rcu_irq_enter(). Let's remove RCU's dependency
64 * on the tick.
65 */
66 vtime_user_enter(current);
67 rcu_user_enter();
68 }
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +010069 /*
Frederic Weisbeckerd65ec122013-07-11 23:59:33 +020070 * Even if context tracking is disabled on this CPU, because it's outside
71 * the full dynticks mask for example, we still have to keep track of the
72 * context transitions and states to prevent inconsistency on those of
73 * other CPUs.
74 * If a task triggers an exception in userspace, sleep on the exception
75 * handler and then migrate to another CPU, that new CPU must know where
76 * the exception returns by the time we call exception_exit().
77 * This information can only be provided by the previous CPU when it called
78 * exception_enter().
79 * OTOH we can spare the calls to vtime and RCU when context_tracking.active
80 * is false because we know that CPU is not tickless.
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +010081 */
Frederic Weisbeckerabf917c2012-07-25 07:56:04 +020082 __this_cpu_write(context_tracking.state, IN_USER);
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +010083 }
84 local_irq_restore(flags);
85}
86
Steven Rostedt29bb9e52013-05-24 15:23:40 -040087#ifdef CONFIG_PREEMPT
88/**
89 * preempt_schedule_context - preempt_schedule called by tracing
90 *
91 * The tracing infrastructure uses preempt_enable_notrace to prevent
92 * recursion and tracing preempt enabling caused by the tracing
93 * infrastructure itself. But as tracing can happen in areas coming
94 * from userspace or just about to enter userspace, a preempt enable
95 * can occur before user_exit() is called. This will cause the scheduler
96 * to be called when the system is still in usermode.
97 *
98 * To prevent this, the preempt_enable_notrace will use this function
99 * instead of preempt_schedule() to exit user context if needed before
100 * calling the scheduler.
101 */
102void __sched notrace preempt_schedule_context(void)
103{
Steven Rostedt29bb9e52013-05-24 15:23:40 -0400104 enum ctx_state prev_ctx;
105
Frederic Weisbeckerfbb00b52013-06-19 23:56:22 +0200106 if (likely(!preemptible()))
Steven Rostedt29bb9e52013-05-24 15:23:40 -0400107 return;
108
109 /*
110 * Need to disable preemption in case user_exit() is traced
111 * and the tracer calls preempt_enable_notrace() causing
112 * an infinite recursion.
113 */
114 preempt_disable_notrace();
115 prev_ctx = exception_enter();
116 preempt_enable_no_resched_notrace();
117
118 preempt_schedule();
119
120 preempt_disable_notrace();
121 exception_exit(prev_ctx);
122 preempt_enable_notrace();
123}
124EXPORT_SYMBOL_GPL(preempt_schedule_context);
125#endif /* CONFIG_PREEMPT */
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +0100126
127/**
128 * user_exit - Inform the context tracking that the CPU is
129 * exiting userspace mode and entering the kernel.
130 *
131 * This function must be called after we entered the kernel from userspace
132 * before any use of RCU read side critical section. This potentially include
133 * any high level kernel code like syscalls, exceptions, signal handling, etc...
134 *
135 * This call supports re-entrancy. This way it can be called from any exception
136 * handler without needing to know if we came from userspace or not.
137 */
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +0100138void user_exit(void)
139{
140 unsigned long flags;
141
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +0100142 if (in_interrupt())
143 return;
144
145 local_irq_save(flags);
146 if (__this_cpu_read(context_tracking.state) == IN_USER) {
Frederic Weisbeckerd65ec122013-07-11 23:59:33 +0200147 if (__this_cpu_read(context_tracking.active)) {
148 /*
149 * We are going to run code that may use RCU. Inform
150 * RCU core about that (ie: we may need the tick again).
151 */
152 rcu_user_exit();
153 vtime_user_exit(current);
154 }
Frederic Weisbeckerabf917c2012-07-25 07:56:04 +0200155 __this_cpu_write(context_tracking.state, IN_KERNEL);
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +0100156 }
157 local_irq_restore(flags);
158}
159
Frederic Weisbecker2d854e52013-07-12 19:02:30 +0200160#ifdef CONFIG_VIRT_CPU_ACCOUNTING_GEN
Frederic Weisbecker6a616712012-12-16 20:00:34 +0100161void guest_enter(void)
162{
163 if (vtime_accounting_enabled())
164 vtime_guest_enter(current);
165 else
Frederic Weisbecker2d854e52013-07-12 19:02:30 +0200166 current->flags |= PF_VCPU;
Frederic Weisbecker6a616712012-12-16 20:00:34 +0100167}
168EXPORT_SYMBOL_GPL(guest_enter);
169
170void guest_exit(void)
171{
172 if (vtime_accounting_enabled())
173 vtime_guest_exit(current);
174 else
Frederic Weisbecker2d854e52013-07-12 19:02:30 +0200175 current->flags &= ~PF_VCPU;
Frederic Weisbecker6a616712012-12-16 20:00:34 +0100176}
177EXPORT_SYMBOL_GPL(guest_exit);
Frederic Weisbecker2d854e52013-07-12 19:02:30 +0200178#endif /* CONFIG_VIRT_CPU_ACCOUNTING_GEN */
Frederic Weisbecker6a616712012-12-16 20:00:34 +0100179
Frederic Weisbecker4eacdf12013-01-16 17:16:37 +0100180
181/**
182 * context_tracking_task_switch - context switch the syscall callbacks
183 * @prev: the task that is being switched out
184 * @next: the task that is being switched in
185 *
186 * The context tracking uses the syscall slow path to implement its user-kernel
187 * boundaries probes on syscalls. This way it doesn't impact the syscall fast
188 * path on CPUs that don't do context tracking.
189 *
190 * But we need to clear the flag on the previous task because it may later
191 * migrate to some CPU that doesn't do the context tracking. As such the TIF
192 * flag may not be desired there.
193 */
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +0100194void context_tracking_task_switch(struct task_struct *prev,
195 struct task_struct *next)
196{
Frederic Weisbeckerd65ec122013-07-11 23:59:33 +0200197 clear_tsk_thread_flag(prev, TIF_NOHZ);
198 set_tsk_thread_flag(next, TIF_NOHZ);
Frederic Weisbecker91d1aa432012-11-27 19:33:25 +0100199}