Kconfig (40565b5aedd6d0ca88b7dfd3859d709d2f6f8cf9) Kconfig (e8f4aa6087fa80732382881ef7c0c96733bb1984)
1#
2# General architecture dependent options
3#
4
5config KEXEC_CORE
6 bool
7
8config OPROFILE

--- 82 unchanged lines hidden (view full) ---

91 depends on DYNAMIC_FTRACE_WITH_REGS
92 help
93 If function tracer is enabled and the arch supports full
94 passing of pt_regs to function tracing, then kprobes can
95 optimize on top of function tracing.
96
97config UPROBES
98 def_bool n
1#
2# General architecture dependent options
3#
4
5config KEXEC_CORE
6 bool
7
8config OPROFILE

--- 82 unchanged lines hidden (view full) ---

91 depends on DYNAMIC_FTRACE_WITH_REGS
92 help
93 If function tracer is enabled and the arch supports full
94 passing of pt_regs to function tracing, then kprobes can
95 optimize on top of function tracing.
96
97config UPROBES
98 def_bool n
99 depends on ARCH_SUPPORTS_UPROBES
99 help
100 Uprobes is the user-space counterpart to kprobes: they
101 enable instrumentation applications (such as 'perf probe')
102 to establish unintrusive probes in user-space binaries and
103 libraries, by executing handler functions when the probes
104 are hit by user-space applications.
105
106 ( These probes come in the form of single-byte breakpoints,

--- 400 unchanged lines hidden (view full) ---

507 the slow path using TIF_NOHZ flag. Exceptions handlers must be
508 wrapped as well. Irqs are already protected inside
509 rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on
510 irq exit still need to be protected.
511
512config HAVE_VIRT_CPU_ACCOUNTING
513 bool
514
100 help
101 Uprobes is the user-space counterpart to kprobes: they
102 enable instrumentation applications (such as 'perf probe')
103 to establish unintrusive probes in user-space binaries and
104 libraries, by executing handler functions when the probes
105 are hit by user-space applications.
106
107 ( These probes come in the form of single-byte breakpoints,

--- 400 unchanged lines hidden (view full) ---

508 the slow path using TIF_NOHZ flag. Exceptions handlers must be
509 wrapped as well. Irqs are already protected inside
510 rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on
511 irq exit still need to be protected.
512
513config HAVE_VIRT_CPU_ACCOUNTING
514 bool
515
515config ARCH_HAS_SCALED_CPUTIME
516 bool
517
518config HAVE_VIRT_CPU_ACCOUNTING_GEN
519 bool
520 default y if 64BIT
521 help
522 With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit.
523 Before enabling this option, arch code must be audited
524 to ensure there are no races in concurrent read/write of
525 cputime_t. For example, reading/writing 64-bit cputime_t on

--- 250 unchanged lines hidden ---
516config HAVE_VIRT_CPU_ACCOUNTING_GEN
517 bool
518 default y if 64BIT
519 help
520 With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit.
521 Before enabling this option, arch code must be audited
522 to ensure there are no races in concurrent read/write of
523 cputime_t. For example, reading/writing 64-bit cputime_t on

--- 250 unchanged lines hidden ---