From: Changqing Li <changqing.li@windriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH V2] ethdev_trace.h: Update the trace point function when _TIME_BITS=64
Date: Sun, 27 Apr 2025 10:06:07 +0800 [thread overview]
Message-ID: <26c063e6-484d-4cae-94c2-b74981c92fe5@windriver.com> (raw)
In-Reply-To: <20250423110052.1b89ad1e@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
On 4/24/25 02:00, Stephen Hemminger wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Tue, 22 Apr 2025 20:29:56 +0800
> <changqing.li@windriver.com> wrote:
>
>> +#if defined(_TIME_BITS) && _TIME_BITS == 64
>> RTE_TRACE_POINT(
>> rte_eth_trace_timesync_write_time,
>> RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *time,
>> int ret),
>> rte_trace_point_emit_u16(port_id);
>> + rte_trace_point_emit_u64(time->tv_sec);
>> + rte_trace_point_emit_long(time->tv_nsec);
>> + rte_trace_point_emit_int(ret);
>> +)
>> +#else
>> +RTE_TRACE_POINT(
>> + rte_eth_trace_timesync_write_time,
>> + RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *time,
>> + int ret),
>> + rte_trace_point_emit_u16(port_id);
>> rte_trace_point_emit_size_t(time->tv_sec);
>> rte_trace_point_emit_long(time->tv_nsec);
>> rte_trace_point_emit_int(ret);
>> )
>> +#endif
> No. Do not start adding #ifdef to trace points.
> Instead, add new hook rte_trace_point_emit_time_t and that can handle
> any ABI changes like this.
Hi, Stephen
Thanks, I will try to add this.
>
> Best to wait until 25.11 release since could be ABI change.
Do you mean I should not send V3 patch? Send the patch after 25.11 is
release?
Regards
Changqing
[-- Attachment #2: Type: text/html, Size: 2357 bytes --]
prev parent reply other threads:[~2025-04-27 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 12:29 changqing.li
2025-04-23 18:00 ` Stephen Hemminger
2025-04-27 2:06 ` Changqing Li [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=26c063e6-484d-4cae-94c2-b74981c92fe5@windriver.com \
--to=changqing.li@windriver.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).