Re: How to display a ktime value as trace timestamp in trace output?

2024-02-29 Thread Steven Rostedt
On Wed, 31 Jan 2024 14:47:31 + David Howells wrote: > Hi Steven, Hi David, Sorry, I just noticed this email as it was buried in other unread emails :-p > > I have a tracepoint in AF_RXRPC that displays information about a timeout I'm > going to set. I have the timeout in a ktime_t as an

[PATCH net-next 1/2] tcp: add tracing of skb/skaddr in tcp_event_sk_skb class

2024-02-29 Thread Jason Xing
From: Jason Xing Prio to this patch, the trace function doesn't print addresses which might be forgotten. As we can see, it already fetches those, use it directly and it will print like below: ...tcp_retransmit_skb: skbaddr=XXX skaddr=XXX family=AF_INET... Signed-off-by: Jason Xing ---

[PATCH net-next 2/2] tcp: add tracing of skbaddr in tcp_event_skb class

2024-02-29 Thread Jason Xing
From: Jason Xing Use the existing parameter and print it then. It will display the address of skbaddr. Signed-off-by: Jason Xing --- include/trace/events/tcp.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/include/trace/events/tcp.h b/include/trace/events/tcp.h index

[PATCH net-next 0/2] add two missing addresses when using trace

2024-02-29 Thread Jason Xing
From: Jason Xing When I reviewed other people's patch [1], I noticed that similar thing also happens in tcp_event_skb class and tcp_event_sk_skb class. They don't print those two addrs of skb/sk which already exist. They are probably forgotten by the original authors, so this time I finish the