ring buffer context: cpu number becomes an output of reserve
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Fri, 26 Mar 2021 17:52:25 +0000 (13:52 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Fri, 26 Mar 2021 20:06:36 +0000 (16:06 -0400)
commit7489fcb466935b3eeb36e99afbbb87188278cb91
tree51f780d44e48dfec9bc1509956c3dbc28fa48f12
parent879f9b0aa0c9a8ee31ba47bfaaf6539ef2e349b2
ring buffer context: cpu number becomes an output of reserve

In order to facilitate eventual integration of a ring buffer scheme
based on Restartable Sequences (sys_rseq), change the ownership of the
ring buffer context "cpu" field so it is now populated by the ring
buffer reserve operation. This means a rseq-based reserve could retry
on a new current cpu after a rseq-cmpxchg fails to reserve and then a
migration occurs.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Change-Id: If0c0689446975085b5e22b14aef6a15f12f8ff9f
include/lttng/ringbuffer-context.h
include/lttng/ust-tracepoint-event.h
liblttng-ust-ctl/ustctl.c
liblttng-ust/lttng-ring-buffer-client.h
libringbuffer/frontend_api.h
libringbuffer/ring_buffer_frontend.c
libringbuffer/ringbuffer-config.h
This page took 0.027087 seconds and 4 git commands to generate.