diff options
| author | Hugh Dickins <hughd@google.com> | 2017-08-23 14:21:14 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-01-05 15:44:24 +0100 |
| commit | 20cbe9a3aa2e341824da57ce0ac6d52cbffaa570 (patch) | |
| tree | ca217cd55ab12d277f752b11b4c96959b1b4c38b /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 487f0b73d82611a2dc48d7d78409e2e9d994006a (diff) | |
kaiser: fix perf crashes
Avoid perf crashes: place debug_store in the user-mapped per-cpu area
instead of allocating, and use page allocator plus kaiser_add_mapping()
to keep the BTS and PEBS buffers user-mapped (that is, present in the
user mapping, though visible only to kernel and hardware). The PEBS
fixup buffer does not need this treatment.
The need for a user-mapped struct debug_store showed up before doing
any conscious perf testing: in a couple of kernel paging oopses on
Westmere, implicating the debug_store offset of the per-cpu area.
Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions
