[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200903121803.75fb0ade@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 3 Sep 2020 12:18:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: sundeep.lkml@...il.com
Cc: davem@...emloft.net, netdev@...r.kernel.org, sgoutham@...vell.com,
Subbaraya Sundeep <sbhatta@...vell.com>
Subject: Re: [net-next PATCH 0/2] Introduce mbox tracepoints for Octeontx2
On Thu, 3 Sep 2020 12:48:16 +0530 sundeep.lkml@...il.com wrote:
> From: Subbaraya Sundeep <sbhatta@...vell.com>
>
> This patchset adds tracepoints support for mailbox.
> In Octeontx2, PFs and VFs need to communicate with AF
> for allocating and freeing resources. Once all the
> configuration is done by AF for a PF/VF then packet I/O
> can happen on PF/VF queues. When an interface
> is brought up many mailbox messages are sent
> to AF for initializing queues. Say a VF is brought up
> then each message is sent to PF and PF forwards to
> AF and response also traverses from AF to PF and then VF.
> To aid debugging, tracepoints are added at places where
> messages are allocated, sent and message interrupts.
> Below is the trace of one of the messages from VF to AF
> and AF response back to VF:
Could you use the devlink tracepoint? trace_devlink_hwmsg() ?
Powered by blists - more mailing lists