From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCHv2 4/4] pmdinfo.py: Add tool to query binaries for hw and other support information Date: Fri, 20 May 2016 10:55:26 +0200 Message-ID: <2679234.W5Qx41Uy7C@xps13> References: <1463431287-4551-1-git-send-email-nhorman@tuxdriver.com> <20160519120031.GC4128@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Neil Horman , dev@dpdk.org, Bruce Richardson , Stephen Hemminger To: Panu Matilainen Return-path: Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by dpdk.org (Postfix) with ESMTP id 696735AB4 for ; Fri, 20 May 2016 10:55:28 +0200 (CEST) Received: by mail-wm0-f47.google.com with SMTP id i142so3459161wmf.0 for ; Fri, 20 May 2016 01:55:28 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-05-20 08:22, Panu Matilainen: > Ability to query individual DSOs is a building block for other things > like automation (you dont expect normal users to go manually loading hw > support modules for the OS either), but its not an end-user solution. > > Thomas said in http://dpdk.org/ml/archives/dev/2016-May/038324.html: > > "This tool should not behave differently depending of how DPDK was > compiled (static or shared)." I meant the basic tool must be usable on static binary and shared library. > Its entirely possible to handle all the three above cases virtually > identically (point the tool to the app executable), so I have a hard > time understanding the level of resistance to handling the plugin case. We need first a basic tool. Then we'll check how to build on it for end user needs. I think you have some good ideas. We could also try (later) to inspect a running DPDK app.