DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
	 Naga Harish K S V <s.v.naga.harish.k@intel.com>,
	 Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	dev@dpdk.org
Subject: Re: [PATCH v2] eventdev: add trace points
Date: Mon, 30 Jan 2023 20:01:55 +0530	[thread overview]
Message-ID: <CALBAE1NBeq5xqYEz_HuR+37_wSvhn8H5NhHWcJ2RgL4Hjj+bDQ@mail.gmail.com> (raw)
In-Reply-To: <20230130101352.1655718-1-amitprakashs@marvell.com>

On Mon, Jan 30, 2023 at 3:44 PM Amit Prakash Shukla
<amitprakashs@marvell.com> wrote:
>
> Add trace points for eventdev functions.
>
> Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> ---

> diff --git a/lib/eventdev/version.map b/lib/eventdev/version.map
> index 4405cd38eb..f6ab242a3d 100644
> --- a/lib/eventdev/version.map
> +++ b/lib/eventdev/version.map
> @@ -121,6 +121,60 @@ EXPERIMENTAL {
>
>         # added in 23.03
>         rte_event_timer_remaining_ticks_get;

Following updates are not needed in version.map based on the
discussion happened ethdev trace thread as it is not required to
expose the symbol.

> +       __rte_eventdev_trace_eth_rx_adapter_caps_get;
> +       __rte_eventdev_trace_eth_tx_adapter_caps_get;
> +       __rte_eventdev_trace_timer_adapter_caps_get;
> +       __rte_eventdev_trace_crypto_adapter_caps_get;
> +       __rte_eventdev_trace_crypto_adapter_event_port_get;
> +       __rte_eventdev_trace_crypto_adapter_service_id_get;
> +       __rte_eventdev_trace_eth_rx_adapter_cb_register;
> +       __rte_eventdev_trace_eth_rx_adapter_create_with_params;
> +       __rte_eventdev_trace_eth_rx_adapter_queue_conf_get;
> +       __rte_eventdev_trace_eth_rx_adapter_service_id_get;
> +       __rte_eventdev_trace_eth_rx_adapter_vector_limits_get;
> +       __rte_eventdev_trace_eth_tx_adapter_event_port_get;
> +       __rte_eventdev_trace_eth_tx_adapter_service_id_get;
> +       __rte_eventdev_trace_port_attr_get;
> +       __rte_eventdev_trace_port_default_conf_get;
> +       __rte_eventdev_trace_port_links_get;
> +       __rte_eventdev_trace_port_quiesce;
> +       __rte_eventdev_trace_port_unlinks_in_progress;
> +       __rte_eventdev_trace_queue_attr_get;
> +       __rte_eventdev_trace_queue_attr_set;
> +       __rte_eventdev_trace_queue_default_conf_get;
> +       __rte_eventdev_trace_ring_create;
> +       __rte_eventdev_trace_ring_free;
> +       __rte_eventdev_trace_ring_init;
> +       __rte_eventdev_trace_ring_lookup;
> +       __rte_eventdev_trace_timer_adapter_get_info;
> +       __rte_eventdev_trace_timer_adapter_lookup;
> +       __rte_eventdev_trace_timer_adapter_service_id_get;
> +       __rte_eventdev_trace_attr_get;
> +       __rte_eventdev_trace_close;
> +       __rte_eventdev_trace_configure;
> +       __rte_eventdev_trace_dump;
> +       __rte_eventdev_trace_get_dev_id;
> +       __rte_eventdev_trace_info_get;
> +       __rte_eventdev_trace_selftest;
> +       __rte_eventdev_trace_service_id_get;
> +       __rte_eventdev_trace_socket_id;
> +       __rte_eventdev_trace_start;
> +       __rte_eventdev_trace_stop;
> +       __rte_eventdev_trace_stop_flush_callback_register;
> +       __rte_eventdev_trace_vector_pool_create;
> +       __rte_eventdev_trace_dequeue_timeout_ticks;
> +       __rte_eventdev_trace_crypto_adapter_stats_get;
> +       __rte_eventdev_trace_crypto_adapter_stats_reset;
> +       __rte_eventdev_trace_eth_rx_adapter_stats_get;
> +       __rte_eventdev_trace_crypto_adapter_vector_limits_get;
> +       __rte_eventdev_trace_eth_rx_adapter_queue_stats_get;
> +       __rte_eventdev_trace_eth_rx_adapter_stats_reset;
> +       __rte_eventdev_trace_eth_rx_adapter_queue_stats_reset;
> +       __rte_eventdev_trace_eth_rx_adapter_event_port_get;
> +       __rte_eventdev_trace_eth_rx_adapter_instance_get;
> +       __rte_eventdev_trace_eth_tx_adapter_stats_get;
> +       __rte_eventdev_trace_eth_tx_adapter_stats_reset;
> +       __rte_eventdev_trace_eth_tx_adapter_instance_get;
>  };
>
>  INTERNAL {
> --
> 2.25.1
>

  reply	other threads:[~2023-01-30 14:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:11 [PATCH] " Amit Prakash Shukla
2023-01-03  5:57 ` Gujjar, Abhinandan S
2023-01-27  9:06   ` Amit Prakash Shukla
2023-01-30 10:13 ` [PATCH v2] " Amit Prakash Shukla
2023-01-30 14:31   ` Jerin Jacob [this message]
2023-01-30 14:52     ` [EXT] " Amit Prakash Shukla
2023-01-30 17:30   ` [PATCH v3] " Amit Prakash Shukla
2023-01-31 13:30     ` [PATCH v4] " Amit Prakash Shukla
2023-01-31 13:44       ` [PATCH v5] " Amit Prakash Shukla
2023-02-01 10:16         ` [EXT] " Shijith Thotton
2023-02-01 10:46           ` Amit Prakash Shukla
2023-02-02  9:17         ` [PATCH v6] " Amit Prakash Shukla
2023-02-02  9:24           ` [EXT] " Shijith Thotton
2023-02-07  8:00             ` Jerin Jacob

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=CALBAE1NBeq5xqYEz_HuR+37_wSvhn8H5NhHWcJ2RgL4Hjj+bDQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=amitprakashs@marvell.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=jerinj@marvell.com \
    --cc=s.v.naga.harish.k@intel.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).