netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, gakula@marvell.com,
	hkelam@marvell.com, sgoutham@marvell.com, lcherian@marvell.com,
	bbhushan2@marvell.com, jerinj@marvell.com,
	netdev@vger.kernel.org
Subject: Re: [net-next PATCH 4/4] octeontx2: Add new tracepoint otx2_msg_status
Date: Mon, 12 May 2025 19:24:26 +0100	[thread overview]
Message-ID: <20250512182426.GV3339421@horms.kernel.org> (raw)
In-Reply-To: <1747039315-3372-6-git-send-email-sbhatta@marvell.com>

On Mon, May 12, 2025 at 02:11:55PM +0530, Subbaraya Sundeep wrote:
> Apart from netdev interface Octeontx2 PF does the following:
> 1. Sends its own requests to AF and receives responses from AF.
> 2. Receives async messages from AF.
> 3. Forwards VF requests to AF, sends respective responses from AF to VFs.
> 4. Sends async messages to VFs.
> This patch adds new tracepoint otx2_msg_status to display the status
> of PF wrt mailbox handling.
> 
> Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
> ---
>  drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.c |  1 +
>  drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.h | 15 +++++++++++++++
>  drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c  | 18 ++++++++++++++++++
>  3 files changed, 34 insertions(+)
> 
> diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.c b/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.c
> index 775fd4c..5f69380 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.c
> +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.c
> @@ -11,3 +11,4 @@
>  EXPORT_TRACEPOINT_SYMBOL(otx2_msg_alloc);
>  EXPORT_TRACEPOINT_SYMBOL(otx2_msg_interrupt);
>  EXPORT_TRACEPOINT_SYMBOL(otx2_msg_process);
> +EXPORT_TRACEPOINT_SYMBOL(otx2_msg_status);
> diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.h b/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.h
> index 721d4a5..e7c2160 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.h
> +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_trace.h
> @@ -118,6 +118,21 @@ TRACE_EVENT(otx2_msg_wait_rsp,
>  		      __get_str(dev))
>  );
>  
> +TRACE_EVENT(otx2_msg_status,
> +	    TP_PROTO(const struct pci_dev *pdev, const char *msg, u16 num_msgs),
> +	    TP_ARGS(pdev, msg, num_msgs),
> +	    TP_STRUCT__entry(__string(dev, pci_name(pdev))
> +			     __string(str, msg)
> +			     __field(u16, num_msgs)
> +	    ),
> +	    TP_fast_assign(__assign_str(dev, pci_name(pdev))
> +			   __assign_str(str, msg)

In order to compile against net-next __assign_str() should
only be passed one argument. Likewise elsewhere in this series.

And, also in order to compile against net-next there needs
to be a ';' after each __assign_str(..).

> +			   __entry->num_msgs = num_msgs;
> +	    ),
> +	    TP_printk("[%s] %s num_msgs:%d\n", __get_str(dev),
> +		      __get_str(str), __entry->num_msgs)
> +);
> +
>  #endif /* __RVU_TRACE_H */
>  
>  #undef TRACE_INCLUDE_PATH

...

-- 
pw-bot: changes-requested

  reply	other threads:[~2025-05-12 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  8:41 [net-next PATCH 0/4] octeontx2: Improve mailbox tracing Subbaraya Sundeep
2025-05-12  8:41 ` [net-next PATCH 1/4] octeontx2-af: convert dev_dbg to tracepoint in mbox Subbaraya Sundeep
2025-05-12 22:29   ` kernel test robot
2025-05-12  8:41 ` [net-next PATCH 2/4] octeontx2-af: Display names for CPT and UP messages Subbaraya Sundeep
2025-05-12  8:41 ` [net-next PATCH 3/4] octeontx2: Add pcifunc also to mailbox tracepoints Subbaraya Sundeep
2025-05-12  8:41 ` [net-next PATCH 3/5] octeontx2: Improve mailbox tracepoints for debugging Subbaraya Sundeep
2025-05-12 18:25   ` Simon Horman
2025-05-13  8:55     ` Subbaraya Sundeep
2025-05-12  8:41 ` [net-next PATCH 4/4] octeontx2: Add new tracepoint otx2_msg_status Subbaraya Sundeep
2025-05-12 18:24   ` Simon Horman [this message]
2025-05-12 23:51   ` kernel test robot

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=20250512182426.GV3339421@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bbhushan2@marvell.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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).