diff options
| author | Markus Metzger <markus.t.metzger@intel.com> | 2008-01-30 07:31:20 -0500 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-01-30 07:31:20 -0500 |
| commit | a95d67f87e1a5f1b4429be3ba3bf7b4051657908 (patch) | |
| tree | 4a67994b901c5dfbf3c2ee752efd53dbce938c36 /arch/m68k/mvme147 | |
| parent | e4811f2568c55e595a7bf15a3b9aba863b31fb94 (diff) | |
x86, ptrace: new ptrace BTS API
Here's the new ptrace BTS API that supports two different overflow handling mechanisms (wrap-around and buffer-full-signal) to support two different use cases (debugging and profiling).
It further combines buffer allocation and configuration.
Opens:
- memory rlimit
- overflow signal
What would be the right signal to use?
Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch/m68k/mvme147')
0 files changed, 0 insertions, 0 deletions