From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 15F18A054F; Tue, 2 Mar 2021 11:14:37 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9DA534014E; Tue, 2 Mar 2021 11:14:37 +0100 (CET) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 41A1F40142 for ; Tue, 2 Mar 2021 11:14:35 +0100 (CET) IronPort-SDR: iOpGfMWmX9zgBmUSKy+C0/l7aGUrJeKQXJmGfuSlw9YLClvQ12vFl1vmzeCWpp6wzngniN8xVg F3v7Tl7XeLaA== X-IronPort-AV: E=McAfee;i="6000,8403,9910"; a="174398739" X-IronPort-AV: E=Sophos;i="5.81,216,1610438400"; d="scan'208";a="174398739" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Mar 2021 02:14:34 -0800 IronPort-SDR: i4NBKiNm6wbdSK0X0zndzsn5tRqenYg8+39PlhgNlad4mSnU/rUWQmPwTLFDhd3UfXSrxanF8F fnUmW/s5ANYA== X-IronPort-AV: E=Sophos;i="5.81,216,1610438400"; d="scan'208";a="444690989" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.19.13]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 02 Mar 2021 02:14:32 -0800 Date: Tue, 2 Mar 2021 10:14:27 +0000 From: Bruce Richardson To: Thomas Monjalon Cc: Kevin Laatz , ciara.power@intel.com, dev@dpdk.org Message-ID: <20210302101427.GB1396@bricha3-MOBL.ger.corp.intel.com> References: <2019455.957uq3bD9f@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2019455.957uq3bD9f@thomas> Subject: Re: [dpdk-dev] telemetry logs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Mar 01, 2021 at 08:22:15PM +0100, Thomas Monjalon wrote: > Hi, > Sorry if I already asked this question. > Would it be possible to use rte_log in rte_telemetry > instead of returning telemetry_log_error at init? > It probably could be made to work by passing in the log function at init time. Haven't delved too much into the details, though.