summaryrefslogtreecommitdiff
path: root/tools/perf/ui/keysyms.h
blob: 65092d576b4e25fb4d8ad7876e6d399492165218 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
#ifndef _PERF_KEYSYMS_H_
#define _PERF_KEYSYMS_H_ 1

#include "libslang.h"

#define K_DOWN	SL_KEY_DOWN
#define K_END	SL_KEY_END
#define K_ENTER	'\r'
#define K_ESC	033
#define K_F1	SL_KEY_F(1)
#define K_HOME	SL_KEY_HOME
#define K_LEFT	SL_KEY_LEFT
#define K_PGDN	SL_KEY_NPAGE
#define K_PGUP	SL_KEY_PPAGE
#define K_RIGHT	SL_KEY_RIGHT
#define K_TAB	'\t'
#define K_UNTAB	SL_KEY_UNTAB
#define K_UP	SL_KEY_UP
#define K_BKSPC 0x7f
#define K_DEL	SL_KEY_DELETE

/* Not really keys */
#define K_TIMER	 -1
#define K_ERROR	 -2
#define K_RESIZE -3
#define K_SWITCH_INPUT_DATA -4

#endif /* _PERF_KEYSYMS_H_ */
it/tree/?h=nds-private-remove&id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>370efda701f03cccf21e02bb1fdd3b852547d75c /net/xfrm/xfrm_ipcomp.c parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'net/xfrm/xfrm_ipcomp.c')