From: Sunil Kumar Kori <skori@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob <jerinj@marvell.com>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>
Subject: RE: [EXTERNAL] [PATCH v3 0/6] Trace point framework enhancement for dmadev
Date: Tue, 11 Feb 2025 08:41:11 +0000 [thread overview]
Message-ID: <CO6PR18MB38605FFEA6694600AA9CF5C9B4FD2@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250210174424.3364021-1-david.marchand@redhat.com>
Hi David,
I validated the series and its functional now. Traces are generated properly.
> dmadev trace points have been working around trace point framework
> limitations.
> One of this workaround blocks enabling dmadev on MSVC.
>
> Traces files were not checked in CI, so this series also adds a new check.
>
> --
> David Marchand
>
> Changes since v2:
> - added check of traces validity in GHA,
> - split patch 2 and fixed CTF metadata,
>
>
> David Marchand (6):
> ci: check traces validity
> trace: support dereferencing arguments
> trace: support expression for blob length
> trace: support dumping binary inside a struct
> dmadev: avoid copies in tracepoints
> trace: fix undefined behavior in register
>
> .ci/linux-build.sh | 10 +++++
> .github/workflows/build.yml | 2 +-
> lib/dmadev/rte_dmadev_trace.h | 32 +++------------
> lib/dmadev/rte_dmadev_trace_fp.h | 26 ++----------
> lib/eal/common/eal_common_trace_ctf.c | 39 ++++++++++++------
> lib/eal/include/rte_trace_point.h | 16 +++++---
> lib/eal/include/rte_trace_point_register.h | 46 +++++++++++++++++++---
> lib/ethdev/ethdev_trace.h | 27 ++++---------
> 8 files changed, 107 insertions(+), 91 deletions(-)
>
> --
> 2.48.1
prev parent reply other threads:[~2025-02-11 8:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 16:14 [PATCH 1/2] trace: support expression for blob length David Marchand
2025-01-24 16:14 ` [PATCH 2/2] dmadev: avoid copies in tracepoints David Marchand
2025-01-27 8:25 ` [EXTERNAL] [PATCH 1/2] trace: support expression for blob length Jerin Jacob
2025-01-30 14:58 ` [PATCH v2 1/3] " David Marchand
2025-01-30 14:58 ` [PATCH v2 2/3] dmadev: avoid copies in tracepoints David Marchand
2025-01-30 14:58 ` [PATCH v2 3/3] trace: fix undefined behavior in register David Marchand
2025-01-30 19:10 ` Stephen Hemminger
2025-01-30 21:06 ` David Marchand
2025-02-07 8:49 ` David Marchand
2025-02-07 11:39 ` [EXTERNAL] " Sunil Kumar Kori
2025-02-10 9:02 ` Sunil Kumar Kori
2025-02-10 9:36 ` David Marchand
2025-02-10 13:37 ` [EXTERNAL] " Jerin Jacob
2025-02-10 14:04 ` David Marchand
2025-02-10 13:38 ` [EXTERNAL] [PATCH v2 1/3] trace: support expression for blob length Jerin Jacob
2025-02-10 17:44 ` [PATCH v3 0/6] Trace point framework enhancement for dmadev David Marchand
2025-02-10 17:44 ` [PATCH v3 1/6] ci: check traces validity David Marchand
2025-02-10 17:44 ` [PATCH v3 2/6] trace: support dereferencing arguments David Marchand
2025-02-11 8:44 ` [EXTERNAL] " Sunil Kumar Kori
2025-02-11 9:53 ` David Marchand
2025-02-10 17:44 ` [PATCH v3 3/6] trace: support expression for blob length David Marchand
2025-02-10 17:44 ` [PATCH v3 4/6] trace: support dumping binary inside a struct David Marchand
2025-02-11 8:52 ` [EXTERNAL] " Sunil Kumar Kori
2025-02-11 9:54 ` David Marchand
2025-02-10 17:44 ` [PATCH v3 5/6] dmadev: avoid copies in tracepoints David Marchand
2025-02-10 17:44 ` [PATCH v3 6/6] trace: fix undefined behavior in register David Marchand
2025-02-11 8:41 ` Sunil Kumar Kori [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=CO6PR18MB38605FFEA6694600AA9CF5C9B4FD2@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@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).