From: Karsten Graul <kgraul@linux.ibm.com>
To: Tony Lu <tonylu@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, guwen@linux.alibaba.com,
dust.li@linux.alibaba.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] net/smc: Introduce tracepoint for smcr link down
Date: Tue, 2 Nov 2021 10:30:22 +0100 [thread overview]
Message-ID: <11f17a34-fd35-f2ec-3f20-dd0c34e55fde@linux.ibm.com> (raw)
In-Reply-To: <20211101073912.60410-4-tonylu@linux.alibaba.com>
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?
next prev parent reply other threads:[~2021-11-02 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 7:39 [PATCH net-next 0/3] Tracepoints for SMC Tony Lu
2021-11-01 7:39 ` [PATCH net-next 1/3] net/smc: Introduce tracepoint for fallback Tony Lu
2021-11-01 7:39 ` [PATCH net-next 2/3] net/smc: Introduce tracepoints for tx and rx msg Tony Lu
2021-11-01 7:39 ` [PATCH net-next 3/3] net/smc: Introduce tracepoint for smcr link down Tony Lu
2021-11-02 9:30 ` Karsten Graul [this message]
2021-11-03 6:57 ` Tony Lu
2021-11-01 13:50 ` [PATCH net-next 0/3] Tracepoints for SMC patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11f17a34-fd35-f2ec-3f20-dd0c34e55fde@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=guwen@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).