From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chuck Lever III <chuck.lever@oracle.com>,
Trond Myklebust <trondmy@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/4] SUNRPC: Replace dprintk() call site in xs_data_ready
Date: Mon, 25 Jul 2022 12:49:20 -0300 [thread overview]
Message-ID: <Yt67gCcZfOEJizay@kernel.org> (raw)
In-Reply-To: <20220722162212.3d080c23@gandalf.local.home>
Em Fri, Jul 22, 2022 at 04:22:12PM -0400, Steven Rostedt escreveu:
> [ Added the user space perf folks ]
>
> On Fri, 22 Jul 2022 18:45:30 +0000
> Chuck Lever III <chuck.lever@oracle.com> wrote:
>
> > >> +TRACE_EVENT(xs_data_ready,
> > >> + TP_PROTO(
> > >> + const struct rpc_xprt *xprt
> > >> + ),
> > >> +
> > >> + TP_ARGS(xprt),
> > >> +
> > >> + TP_STRUCT__entry(
> > >> + __sockaddr(addr, xprt->addrlen)
> > >> + ),
> > >> +
> > >> + TP_fast_assign(
> > >> + __assign_sockaddr(addr, &xprt->addr, xprt->addrlen);
> > >> + ),
> > >> +
> > >> + TP_printk("peer=%pISpc", __get_sockaddr(addr))
> > >
> > > NACK. Please resolve and store the string up front instead of storing
> > > the sockaddr. Most versions of perf can't resolve those kernel-specific
> > > %p printks and just end up barfing on them.
> >
> > Interesting. We added get_sockaddr() to avoid this issue in
> > trace-cmd. Sounds like perf needs to be fixed up too, or
> > maybe this is another case of having an old libtraceevent?
> >
> > Meanwhile, I can revert this back to the old way of handling
> > presentation addresses.
> >
>
> Hmm, I thought that perf now uses the external libtraceevent.
>
> Perhaps it hasn't been updated to the latest release that has the ability
> to parse this.
>
> Maybe just install
>
> git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
To use it one has to use:
make -C tools/perf LIBTRACEEVENT_DYNAMIC=1
Then we get it linked with libtraceevent-devel:
$ ldd ~/bin/perf | grep traceevent
libtraceevent.so.1 => /lib64/libtraceevent.so.1 (0x00007faa50f93000)
$
Perhaps it'd be better to check if libtracevent-devel is installed and
use it, falling back to tools/lib/traceevent/ and then adding a warning
that the in-tree codebase is being used?
- Arnaldo
next prev parent reply other threads:[~2022-07-25 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165851065336.361126.17865870911497306083.stgit@morisot.1015granger.net>
[not found] ` <165851074247.361126.17205394769981595871.stgit@morisot.1015granger.net>
[not found] ` <66371b9db4210fe853e98a8ec68b0f780ba886af.camel@hammerspace.com>
[not found] ` <9FDA46D8-4D6E-49B0-A583-D0FF739111BF@oracle.com>
2022-07-22 20:22 ` [PATCH 3/4] SUNRPC: Replace dprintk() call site in xs_data_ready Steven Rostedt
2022-07-25 15:49 ` Arnaldo Carvalho de Melo [this message]
2022-07-25 16:06 ` Steven Rostedt
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=Yt67gCcZfOEJizay@kernel.org \
--to=acme@kernel.org \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=trondmy@hammerspace.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).