DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: WanRenyong <wanry@yunsilicon.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com
Subject: Re: [PATCH v3 02/19] net/xsc: add log macro
Date: Wed, 18 Sep 2024 10:56:35 +0200	[thread overview]
Message-ID: <CAJFAV8wNfmvoMMgOzYsTXC4EOe6tXCnqK6D3HG3xv5=ouC-3tw@mail.gmail.com> (raw)
In-Reply-To: <20240918060936.1231758-3-wanry@yunsilicon.com>

On Wed, Sep 18, 2024 at 8:10 AM WanRenyong <wanry@yunsilicon.com> wrote:
>
> Add log macro to print runtime messages and trace functions.
>
> Signed-off-by: WanRenyong <wanry@yunsilicon.com>
>
> ---
>
> v3:
> * use RTE_LOG_LINE_PREFIX instead of rte_log
> ---
>  drivers/net/xsc/xsc_ethdev.c | 11 +++++++++
>  drivers/net/xsc/xsc_log.h    | 46 ++++++++++++++++++++++++++++++++++++
>  2 files changed, 57 insertions(+)
>  create mode 100644 drivers/net/xsc/xsc_log.h
>
> diff --git a/drivers/net/xsc/xsc_ethdev.c b/drivers/net/xsc/xsc_ethdev.c
> index 0e48cb76fa..58ceaa3940 100644
> --- a/drivers/net/xsc/xsc_ethdev.c
> +++ b/drivers/net/xsc/xsc_ethdev.c
> @@ -1,3 +1,14 @@
>  /* SPDX-License-Identifier: BSD-3-Clause
>   * Copyright 2024 Yunsilicon Technology Co., Ltd.
>   */
> +
> +#include "xsc_log.h"
> +
> +RTE_LOG_REGISTER_SUFFIX(xsc_logtype_init, init, NOTICE);
> +RTE_LOG_REGISTER_SUFFIX(xsc_logtype_driver, driver, NOTICE);
> +#ifdef RTE_ETHDEV_DEBUG_RX
> +RTE_LOG_REGISTER_SUFFIX(xsc_logtype_rx, rx, DEBUG);
> +#endif
> +#ifdef RTE_ETHDEV_DEBUG_TX
> +RTE_LOG_REGISTER_SUFFIX(xsc_logtype_tx, tx, DEBUG);
> +#endif
> diff --git a/drivers/net/xsc/xsc_log.h b/drivers/net/xsc/xsc_log.h
> new file mode 100644
> index 0000000000..99a88fcd1b
> --- /dev/null
> +++ b/drivers/net/xsc/xsc_log.h
> @@ -0,0 +1,46 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright 2024 Yunsilicon Technology Co., Ltd.
> + */
> +
> +#ifndef _XSC_LOG_H_
> +#define _XSC_LOG_H_
> +
> +#include <rte_log.h>
> +
> +extern int xsc_logtype_init;
> +extern int xsc_logtype_driver;
> +#define RTE_LOGTYPE_XSC_INIT xsc_logtype_init
> +#define RTE_LOGTYPE_XSC_DRV xsc_logtype_driver
> +
> +
> +#define PMD_INIT_LOG(level, ...) \
> +       RTE_LOG_LINE_PREFIX(level, XSC_INIT, "%s(): ", __func__, __VA_ARGS__)

Thank you for converting to RTE_LOG_LINE!

> +
> +
> +#define PMD_INIT_FUNC_TRACE() PMD_INIT_LOG(DEBUG, " >>")
> +
> +#ifdef RTE_ETHDEV_DEBUG_RX
> +extern int xsc_logtype_rx;
> +#define RTE_LOGTYPE_XSC_RX xsc_logtype_rx
> +#define PMD_RX_LOG(level, ...) \
> +       RTE_LOG_LINE_PREFIX(level, XSC_RX, "%s(): ", __func__, __VA_ARGS__)
> +#else
> +#define PMD_RX_LOG(level, ...) do { } while (0)
> +#endif
> +
> +#ifdef RTE_ETHDEV_DEBUG_TX
> +extern int xsc_logtype_tx;
> +#define RTE_LOGTYPE_XSC_TX xsc_logtype_tx
> +#define PMD_TX_LOG(level, ...) \
> +       RTE_LOG_LINE_PREFIX(level, XSC_TX, "%s(): ", __func__, __VA_ARGS__)
> +#else
> +#define PMD_TX_LOG(level, ...) do { } while (0)
> +#endif

I don't see any code calling those macros in the series, so I would
remove them for now.
You can introduce them in the future when needed.


> +
> +#define PMD_DRV_LOG_RAW(level, ...) \
> +       RTE_LOG_LINE_PREFIX(level, XSC_DRV, "%s(): ", __func__, __VA_ARGS__)
> +
> +#define PMD_DRV_LOG(level, ...) \
> +       PMD_DRV_LOG_RAW(level, __VA_ARGS__)

The PMD_DRV_LOG_RAW macro seems unused and can be removed =>
PMD_DRV_LOG() directly calls RTE_LOG_LINE_PREFIX().


-- 
David Marchand


  reply	other threads:[~2024-09-18  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  6:09 WanRenyong
2024-09-18  8:56 ` David Marchand [this message]
2024-09-18  9:28   ` WanRenyong

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='CAJFAV8wNfmvoMMgOzYsTXC4EOe6tXCnqK6D3HG3xv5=ouC-3tw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=wanry@yunsilicon.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).