From: Jason Gunthorpe <jgg@nvidia.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] IB CM tracepoints
Date: Fri, 31 Jul 2020 16:07:10 -0300 [thread overview]
Message-ID: <20200731190710.GA520925@nvidia.com> (raw)
In-Reply-To: <159526519212.1543.15414933891659731269.stgit@klimt.1015granger.net>
On Mon, Jul 20, 2020 at 01:16:28PM -0400, Chuck Lever wrote:
> Oracle has an interest in a common observability infrastructure in
> the RDMA core and ULPs. Introduce static tracepoints that can also
> be used as hooks for eBPF scripts, replacing infrastructure that
> is based on printk. This takes the same approach as tracepoints
> added recently in the RDMA CM.
>
> Changes since RFC:
> * Correct spelling of example tracepoint in patch description
> * Newer tool chains don't care for tracepoints with the same name
> in different subsystems
> * Display ib_cm_events, not ib_events
>
>
> Chuck Lever (3):
> RDMA/core: Move the rdma_show_ib_cm_event() macro
> RDMA/cm: Replace pr_debug() call sites with tracepoints
> RDMA/cm: Add tracepoints to track MAD send operations
>
>
> drivers/infiniband/core/Makefile | 2 +-
> drivers/infiniband/core/cm.c | 102 ++++---
> drivers/infiniband/core/cm_trace.c | 15 ++
> drivers/infiniband/core/cm_trace.h | 414 +++++++++++++++++++++++++++++
> 4 files changed, 476 insertions(+), 57 deletions(-)
> create mode 100644 drivers/infiniband/core/cm_trace.c
> create mode 100644 drivers/infiniband/core/cm_trace.h
This doesn't apply, can you resend it?
Applying: RDMA/core: Move the rdma_show_ib_cm_event() macro
error: sha1 information is lacking or useless (include/trace/events/rpcrdma.h).
error: could not build fake ancestor
Patch failed at 0001 RDMA/core: Move the rdma_show_ib_cm_event() macro
hint: Use 'git am --show-current-patch=diff' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
I guess in two weeks after the merge window
Thanks,
Jason
prev parent reply other threads:[~2020-07-31 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:16 [PATCH v2 0/3] IB CM tracepoints Chuck Lever
2020-07-20 17:16 ` [PATCH v2 1/3] RDMA/core: Move the rdma_show_ib_cm_event() macro Chuck Lever
2020-07-20 17:16 ` [PATCH v2 2/3] RDMA/cm: Replace pr_debug() call sites with tracepoints Chuck Lever
2020-07-20 17:16 ` [PATCH v2 3/3] RDMA/cm: Add tracepoints to track MAD send operations Chuck Lever
2020-07-31 19:07 ` Jason Gunthorpe [this message]
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=20200731190710.GA520925@nvidia.com \
--to=jgg@nvidia.com \
--cc=chuck.lever@oracle.com \
--cc=linux-rdma@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.