Perf counter context info needs to be at fixed addresses v2.0-pre2
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 26 Jul 2011 15:40:12 +0000 (11:40 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 26 Jul 2011 15:40:12 +0000 (11:40 -0400)
commit2001023e1ab9ae4bf85cad1dfb4c9aefb2e40dcf
tree58d28adaf42552971d7ff9f5b1bb18dad286da23
parent4cae220c1be2cc73008603a21152fce7643cfc35
Perf counter context info needs to be at fixed addresses

Fixes a kernel oops when using perf counter with multiple contexts. The
cpu hotplug notifier callback needs to have the callback notifier block
at a fixed address, but the context array may move as it is expanded.

The reason why we use a context array instead of an array of pointers is
to minimize the amount of memory accesses in the tracing hot path.

Let's special-case perf counters and put them in their own memory region
to account for cpu hotplug requirements.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
ltt-context.c
ltt-events.h
lttng-context-perf-counters.c
This page took 0.028103 seconds and 4 git commands to generate.