rxrpc: trace: Don't use __builtin_return_address for rxrpc_peer tracing
In rxrpc tracing, use enums to generate lists of points of interest rather
than __builtin_return_address() for the rxrpc_peer tracepoint
Signed-off-by:
David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
Showing
- include/trace/events/rxrpc.h 26 additions, 17 deletionsinclude/trace/events/rxrpc.h
- net/rxrpc/af_rxrpc.c 1 addition, 1 deletionnet/rxrpc/af_rxrpc.c
- net/rxrpc/ar-internal.h 6 additions, 5 deletionsnet/rxrpc/ar-internal.h
- net/rxrpc/call_accept.c 5 additions, 3 deletionsnet/rxrpc/call_accept.c
- net/rxrpc/call_object.c 1 addition, 1 deletionnet/rxrpc/call_object.c
- net/rxrpc/conn_client.c 4 additions, 4 deletionsnet/rxrpc/conn_client.c
- net/rxrpc/conn_object.c 1 addition, 1 deletionnet/rxrpc/conn_object.c
- net/rxrpc/peer_event.c 4 additions, 4 deletionsnet/rxrpc/peer_event.c
- net/rxrpc/peer_object.c 16 additions, 18 deletionsnet/rxrpc/peer_object.c
- net/rxrpc/sendmsg.c 1 addition, 1 deletionnet/rxrpc/sendmsg.c
Loading
Please register or sign in to comment