From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com [209.85.192.173]) by dpdk.org (Postfix) with ESMTP id 18518591A for ; Tue, 19 Jan 2016 22:35:08 +0100 (CET) Received: by mail-pf0-f173.google.com with SMTP id q63so187241789pfb.1 for ; Tue, 19 Jan 2016 13:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=zbCMOhOK6HrUCqGuTN4AF+WxAV+2ngL/2vFZq8dLcPU=; b=CSpfRE5Ep4YpiN+X0ixFJDa3O1G5gi1xslRQavtmlPQmxYdQjz0gTF4v+9g8mJPdO6 tw/F4gwYSwKgkW/WddTFLH6iPK/JpG2oYY0fK1GB6WgzB1xdoWhMS3gKzkdNge74IEHE cVrOc0QaR/IMU5PTGHr9R3yxRaYwN7SLo35tpEEjbvmF6c/gD1jkxQm2vSU8QHUSEOEG s44lyvE2sPgzwjP3NS1nH+LUsWSJx75+wsoMjGxxUy7i8eCsaXsO1YiBCnNnB2t8VWDY sj5l95gaww0qnrfyp0669AJ37K3VLrBtHnd+WmO9GhXwPUtH4g03LBYJWWNIkzyHarKL Mwmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=zbCMOhOK6HrUCqGuTN4AF+WxAV+2ngL/2vFZq8dLcPU=; b=b5QcyQd/c2N7bkmdIQjKUTeyH3w8z8dAdJvoGV7R4GCUI/cdBnQrLTS9q3ED3g2NMF gXz+cc4W5vEMKJlRzyk1p+F6VlHLGLeMX7fLodsDQmS39pmFmqVeQuGdJPnbmho665p3 CSHlJJQb4HWzG3uwvytaqXTjIW+EDxdzOzgLDuU9IhTZrW9WlLLdEFOzzCNeQ8/3XNB2 uHJbmNKpf3XeQIzd8Nc31vmapvbEy18qVGA98/OJM2IO4nMoqBdNA2cOyVZ+tYUm48qH 9DjXaPyV9+NVKFFv2zsc0lalnCjL8o+gLTmewK1IV5c167WnDFMOmr99QAyqoVdoJ+w2 DaEw== X-Gm-Message-State: ALoCoQnSs6MvqoUZFxBPrqvNg7qg6dSVDH9cS7BY8HJQ4wDMdyk4UV4akxG0zX1EIJ0vaFD5Xfq8DIYcM2BhXL68whx+PmWf3w== X-Received: by 10.98.79.4 with SMTP id d4mr46841653pfb.46.1453239307358; Tue, 19 Jan 2016 13:35:07 -0800 (PST) Received: from xeon-e3 (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id a62sm34701367pfj.40.2016.01.19.13.35.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jan 2016 13:35:07 -0800 (PST) Date: Tue, 19 Jan 2016 13:35:14 -0800 From: Stephen Hemminger To: Neil Horman Message-ID: <20160119133514.03cf193f@xeon-e3> In-Reply-To: <20160119205614.GA24277@hmsreliant.think-freely.org> References: <1452430254-30390-1-git-send-email-david.marchand@6wind.com> <1453120248-28274-1-git-send-email-david.marchand@6wind.com> <1453120248-28274-11-git-send-email-david.marchand@6wind.com> <3759018.lgeOm8Q2D2@xps13> <20160119142930.GA25388@hmsreliant.think-freely.org> <20160119081019.607a9b48@xeon-e3> <20160119205614.GA24277@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org, Neil Horman Subject: Re: [dpdk-dev] [PATCH v2 10/10] pci: place all uio pci device ids in a dedicated section X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 21:35:08 -0000 On Tue, 19 Jan 2016 15:56:14 -0500 Neil Horman wrote: > On Tue, Jan 19, 2016 at 08:10:19AM -0800, Stephen Hemminger wrote: > > On Tue, 19 Jan 2016 09:29:31 -0500 > > Neil Horman wrote: > >=20 > > > On Tue, Jan 19, 2016 at 08:30:40AM +0100, Thomas Monjalon wrote: > > > > 2016-01-18 13:30, David Marchand: > > > > > We could do something =C3=A0 la modinfo, but let's keep it simple= for now. > > > > >=20 > > > > > With this, you can extract the devices that need to be bound to u= io / vfio > > > > > with tools like objdump : > > > > >=20 > > > > > $ objdump -j rte_pci_id_uio -s build/lib/librte_pmd_fm10k.so > > > > >=20 > > > > > Contents of section rte_pci_id_uio: > > > > > 15760 8680a415 ffffffff 8680d015 ffffffff ................ > > > > > 15770 8680a515 ffffffff 00000000 00000000 ................ > > > >=20 > > > > Yes we need a modinfo-like tool. > > > > Currently, the UIO/VFIO binding can be done after parsing the PCI d= evice list. > > > > It is better to define the device ids locally to their drivers but = it must > > > > be integrated with an appropriate parsing tool at the same time. > > > > And more importantly than any tool, the format of these ELF data mu= st be > > > > properly defined, documented and extensible. > > > >=20 > > > > Is there someone experimented with such format definition? > > > > Stephen, you were asking for this change, what is your opinion? > > > > I remember that Neil was also interested in this change: > > > > http://dpdk.org/ml/archives/dev/2015-January/012115.html > > > > Panu, Christian, this change could be related to distribution packa= ging. > > > > Thanks for helping to move this change forward. > > >=20 > > > Yes, I would be interested in seeing this. Is the ask here that some= one do it? > > > As I recall from the last thread that you reference, I thought David = M was > > > interested in writing it and soliciting for ideas. If thats no longe= r the case, > > > I can take a stab at writing it. > > >=20 > > > Neil > > >=20 > >=20 > > If these are libraries is there a way to have a real entry point > > to dump PCI id's.=20 > >=20 > Sure, you could write a method that could be dlsym-ed easily enough to fe= tch an > array of pci ids, or just print stuff the console. Not sure thats the be= st way, > but definately an option > Neil It is just that reading data with objdump is a kludge likely to get broken.