public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Simon Horman <horms@kernel.org>
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 3/5] octeontx2: Improve mailbox tracepoints for debugging
Date: Tue, 13 May 2025 08:55:57 +0000	[thread overview]
Message-ID: <aCMJHfYbws-amobR@f65018e88ba3> (raw)
In-Reply-To: <20250512182544.GW3339421@horms.kernel.org>

Hi Simon,

On 2025-05-12 at 18:25:44, Simon Horman (horms@kernel.org) wrote:
> On Mon, May 12, 2025 at 02:11:54PM +0530, Subbaraya Sundeep wrote:
> > There are various stages involved when a VF sends a message
> > to AF. Say for a VF to send a message to AF below are the steps:
> > 1. VF sends message to PF
> > 2. PF receives interrupt from VF
> > 3. PF forwards to AF
> > 4. AF processes it and sends response back to PF
> > 5. PF sends 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 to check which
> > message is sent at any point of time from a device.
> > 
> > Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
> 
> The cover letter and other patches in this series are n/4.
> But this is patch 3/5 (there is also a patch 3/4).
> This doesn't seem right.
Yes you are right. Some stale patch in the directory sent by mistake.
Please ignore this. Will send v2.

Thanks,
Sundeep

  reply	other threads:[~2025-05-13  8:56 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 [this message]
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
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=aCMJHfYbws-amobR@f65018e88ba3 \
    --to=sbhatta@marvell.com \
    --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=horms@kernel.org \
    --cc=jerinj@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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