DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ciara Power <ciara.power@intel.com>
Cc: "Laatz, Kevin" <kevin.laatz@intel.com>, dpdk-dev <dev@dpdk.org>,
	 Jerin Jacob <jerinj@marvell.com>,
	David Marchand <david.marchand@redhat.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	 "Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] [PATCH] telemetry: fix error and warning printfs
Date: Fri, 22 May 2020 22:04:44 +0530	[thread overview]
Message-ID: <CALBAE1P3cGPvOWZbBxPDswL=q3H6iWJgebYmdhz=PX2kGCVDfg@mail.gmail.com> (raw)
In-Reply-To: <20200522134839.15911-1-ciara.power@intel.com>

On Fri, May 22, 2020 at 7:21 PM Ciara Power <ciara.power@intel.com> wrote:
>
> Initially, printf was used to indicate and error/warning resulting from
> telemetry initialisation. This is now fixed to use EAL logs for
> warnings, and the unnecessary printf for an error is removed.
>
> Fixes: eeb486f3ba65 ("eal: add telemetry as dependency")
> Fixes: dd6275a424ac ("telemetry: fix error log output")
> Cc: david.marchand@redhat.com
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> ---
>  lib/librte_eal/freebsd/eal.c         | 4 +++-
>  lib/librte_eal/linux/eal.c           | 4 +++-
>  lib/librte_telemetry/rte_telemetry.h | 9 +++++++++
>  lib/librte_telemetry/telemetry.c     | 2 --
>  4 files changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/lib/librte_eal/freebsd/eal.c b/lib/librte_eal/freebsd/eal.c
> index 14b52168e..07456059e 100644
> --- a/lib/librte_eal/freebsd/eal.c
> +++ b/lib/librte_eal/freebsd/eal.c
> @@ -956,13 +956,15 @@ rte_eal_init(int argc, char **argv)
>                 return -1;
>         }
>         if (!internal_config.no_telemetry) {
> -               const char *error_str;
> +               const char *error_str = NULL;
>                 if (rte_telemetry_init(rte_eal_get_runtime_dir(),
>                                 &internal_config.ctrl_cpuset, &error_str)
>                                 != 0) {
>                         rte_eal_init_alert(error_str);
>                         return -1;
>                 }
> +               if (error_str != NULL)
> +                       RTE_LOG(WARNING, EAL, "%s\n", error_str);
>         }
>
>         eal_mcfg_complete();
> diff --git a/lib/librte_eal/linux/eal.c b/lib/librte_eal/linux/eal.c
> index 9620d2544..10317a660 100644
> --- a/lib/librte_eal/linux/eal.c
> +++ b/lib/librte_eal/linux/eal.c
> @@ -1294,13 +1294,15 @@ rte_eal_init(int argc, char **argv)
>                 return -1;
>         }
>         if (!internal_config.no_telemetry) {
> -               const char *error_str;
> +               const char *error_str = NULL;
>                 if (rte_telemetry_init(rte_eal_get_runtime_dir(),
>                                 &internal_config.ctrl_cpuset, &error_str)
>                                 != 0) {
>                         rte_eal_init_alert(error_str);
>                         return -1;
>                 }
> +               if (error_str != NULL)
> +                       RTE_LOG(WARNING, EAL, "%s\n", error_str);

"EAL: No legacy callbacks, legacy socket not created" comes all the times now.
Should we treat this as a warning? as it comes for with for the
built-in applications?
If it is important why not have a default handler in the EAL library?


>         }
>
>         eal_mcfg_complete();
> diff --git a/lib/librte_telemetry/rte_telemetry.h b/lib/librte_telemetry/rte_telemetry.h
> index 2c3c96cf7..eb7f2c917 100644
> --- a/lib/librte_telemetry/rte_telemetry.h
> +++ b/lib/librte_telemetry/rte_telemetry.h
> @@ -241,8 +241,17 @@ int
>  rte_telemetry_register_cmd(const char *cmd, telemetry_cb fn, const char *help);
>
>  /**
> + * @internal
>   * Initialize Telemetry.
>   *
> + * @param runtime_dir
> + * The runtime directory of DPDK.
> + * @param cpuset
> + * The CPU set to be used for setting the thread affinity.
> + * @param err_str
> + * This err_str pointer should point to NULL on entry. In the case of an error
> + * or warning, it will be non-NULL on exit.
> + *
>   * @return
>   *  0 on success.
>   * @return
> diff --git a/lib/librte_telemetry/telemetry.c b/lib/librte_telemetry/telemetry.c
> index 7b6f8a79e..e7e3d861d 100644
> --- a/lib/librte_telemetry/telemetry.c
> +++ b/lib/librte_telemetry/telemetry.c
> @@ -403,12 +403,10 @@ rte_telemetry_init(const char *runtime_dir, rte_cpuset_t *cpuset,
>  {
>         if (telemetry_v2_init(runtime_dir, cpuset) != 0) {
>                 *err_str = telemetry_log_error;
> -               printf("Error initialising telemetry - %s\n", *err_str);
>                 return -1;
>         }
>         if (telemetry_legacy_init(runtime_dir, cpuset) != 0) {
>                 *err_str = telemetry_log_error;
> -               printf("No telemetry legacy support - %s\n", *err_str);
>         }
>         return 0;
>  }
> --
> 2.17.1
>

  parent reply	other threads:[~2020-05-22 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 13:48 Ciara Power
2020-05-22 15:00 ` Bruce Richardson
2020-05-22 16:34 ` Jerin Jacob [this message]
2020-05-22 16:48   ` Bruce Richardson
2020-05-22 17:00     ` Jerin Jacob
2020-05-24 16:05     ` Thomas Monjalon
2020-05-25  9:55       ` Bruce Richardson

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='CALBAE1P3cGPvOWZbBxPDswL=q3H6iWJgebYmdhz=PX2kGCVDfg@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=keith.wiles@intel.com \
    --cc=kevin.laatz@intel.com \
    --cc=thomas@monjalon.net \
    /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).