From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC914C4338F for ; Thu, 29 Jul 2021 15:48:53 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 17CD760F43 for ; Thu, 29 Jul 2021 15:48:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 17CD760F43 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EE6E440687; Thu, 29 Jul 2021 17:48:51 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id 2C98B4067A for ; Thu, 29 Jul 2021 17:48:49 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10060"; a="211029759" X-IronPort-AV: E=Sophos;i="5.84,278,1620716400"; d="scan'208";a="211029759" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2021 08:48:48 -0700 X-IronPort-AV: E=Sophos;i="5.84,278,1620716400"; d="scan'208";a="664445221" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.31.36]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 29 Jul 2021 08:48:46 -0700 Date: Thu, 29 Jul 2021 16:48:42 +0100 From: Bruce Richardson To: Gowrishankar Muthukrishnan Cc: dev@dpdk.org, ciara.power@intel.com, jerinj@marvell.com, kirankumark@marvell.com, ndabilpuram@marvell.com, skori@marvell.com, skoteshwar@marvell.com Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [v1, 1/3] telemetry: enable storing pointer value 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 Thu, Jul 29, 2021 at 08:55:35PM +0530, Gowrishankar Muthukrishnan wrote: > At present, value of pointer variable or address can only be > stored in u64 type which is slightly not human readable, hence > this patch is. It adds telemetry support to store pointer value, > which is stringified. > > Signed-off-by: Gowrishankar Muthukrishnan > --- I'm a little curious as to the usefulness of having a pointer value in telemetry output? How would a telemetry user be expected to use pointer information returned? Printing pointers seems something more useful for a debugging or tracing interface than a telemetry one. Regards, /Bruce