The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Subbaraya Sundeep <sbhatta@marvell.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Sunil Goutham <sgoutham@marvell.com>,
	Linu Cherian <lcherian@marvell.com>,
	Geetha sowjanya <gakula@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>, hariprasad <hkelam@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>
Subject: Re: [net-next PATCH] octeontx2: Improve mailbox tracepoints for debugging
Date: Thu, 30 May 2024 11:23:55 -0700	[thread overview]
Message-ID: <8363b014-dd75-4dfc-a248-85a2aa129cce@intel.com> (raw)
In-Reply-To: <1717070038-18381-1-git-send-email-sbhatta@marvell.com>



On 5/30/2024 4:53 AM, Subbaraya Sundeep wrote:
> The tracepoints present currently wrt mailbox do not
> provide enough information to debug mailbox activity.
> For a VF to send a message to AF, VF sends message to PF
> and PF forwards it to AF. This involves stages of
> PF receiving interrupt from VF, forwarding to AF, AF
> processing and sending response back to PF, PF sending back
> the response to VF. This patch adds pcifunc which represents
> PF and VF device to the tracepoints otx2_msg_alloc,
> otx2_msg_send, otx2_msg_process so that it is easier
> to correlate which device allocated the message, which
> device forwarded it and which device processed that message.
> Also add message id in otx2_msg_send tracepoint and new
> tracepoint otx2_msg_status to display the status at each
> stage.
> 
> Below is the trace log when a VF sends a message to AF with
> this patch in place:
> 
> ifconfig-523 [001] ....   146.134718: otx2_msg_alloc: [0002:05:00.1]
> 	msg:(NIX_RSS_FLOWKEY_CFG) size:28 pcifunc:0x1001
> 
> ifconfig-523 [001] ...1   146.134719: otx2_msg_send: [0002:05:00.1]
> 	sent 1 msg(s) of size:32 msg:(NIX_RSS_FLOWKEY_CFG) pcifunc:0x1001
> 
>   <idle>-0 [000] d.h1   146.134722: otx2_msg_interrupt: [0002:05:00.0]
> 	mbox interrupt VF(s) to PF (0x1)
> 
> kworker/u49:2-238 [002] ....   146.134723: otx2_msg_status: [0002:05:00.0]
> 	PF-VF down queue handler(forwarding) num_msgs:1
> 
> kworker/u49:2-238 [002] ...1   146.134724: otx2_msg_send: [0002:05:00.0]
> 	sent 1 msg(s) of size:32 msg:(NIX_RSS_FLOWKEY_CFG) pcifunc:0x1001
> 
>   <idle>-0 [000] d.h1   146.134726: otx2_msg_interrupt: [0002:01:00.0]
> 	mbox interrupt PF(s) to AF (0x10)
> 
> kworker/u49:1-184 [000] ....   146.134739: otx2_msg_process: [0002:01:00.0]
> 	msg:(NIX_RSS_FLOWKEY_CFG) error:0 pcifunc:0x1001
> 
> kworker/u49:1-184 [000] ...1   146.134740: otx2_msg_send: [0002:01:00.0]
> 	sent 1 msg(s) of size:32 msg:(NIX_RSS_FLOWKEY_CFG) pcifunc:0x1001
> 
>   <idle>-0 [000] dNh2   146.134742: otx2_msg_interrupt: [0002:05:00.0]
> 	mbox interrupt DOWN reply from AF to PF (0x1)
> 
>   <idle>-0 [000] dNh2   146.134742: otx2_msg_status: [0002:05:00.0]
> 	PF-AF down work queued(interrupt) num_msgs:1
> 
> kworker/u49:1-184 [000] ....   146.134743: otx2_msg_status: [0002:05:00.0]
> 	PF-AF down queue handler(response) num_msgs:1
> 
>   <idle>-0 [000] d.h1   146.135730: otx2_msg_interrupt: [0002:05:00.1]
> 	mbox interrupt DOWN reply from PF to VF (0x1)
> 
> Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>

Makes sense.

Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

  reply	other threads:[~2024-05-30 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 11:53 [net-next PATCH] octeontx2: Improve mailbox tracepoints for debugging Subbaraya Sundeep
2024-05-30 18:23 ` Jacob Keller [this message]
2024-05-30 19:48 ` kernel test robot
2024-05-30 20: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=8363b014-dd75-4dfc-a248-85a2aa129cce@intel.com \
    --to=jacob.e.keller@intel.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=linux-kernel@vger.kernel.org \
    --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