[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11f17a34-fd35-f2ec-3f20-dd0c34e55fde@linux.ibm.com>
Date: Tue, 2 Nov 2021 10:30:22 +0100
From: Karsten Graul <kgraul@...ux.ibm.com>
To: Tony Lu <tonylu@...ux.alibaba.com>
Cc: kuba@...nel.org, davem@...emloft.net, guwen@...ux.alibaba.com,
dust.li@...ux.alibaba.com, netdev@...r.kernel.org,
linux-s390@...r.kernel.org, linux-rdma@...r.kernel.org
Subject: Re: [PATCH net-next 3/3] net/smc: Introduce tracepoint for smcr link
down
On 01/11/2021 08:39, Tony Lu wrote:
> +
> + TP_printk("lnk=%p lgr=%p state=%d dev=%s location=%p",
> + __entry->lnk, __entry->lgr,
> + __entry->state, __get_str(name),
> + __entry->location)
The location is printed as pointer (which might even be randomized?),
is it possible to print the function name of the caller, as described
here: https://stackoverflow.com/questions/4141324/function-caller-in-linux-kernel
printk("Caller is %pS\n", __builtin_return_address(0));
Not sure if this is possible with the trace points, but it would be
easier to use. You plan to use a dump to find out about the function caller?
Powered by blists - more mailing lists