From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 2/3] eal: PCI domain should be 32 bits Date: Thu, 22 Jun 2017 18:05:42 +0200 Message-ID: <3793478.bOXkPGkn7S@xps> References: <20170622155641.25916-1-stephen@networkplumber.org> <20170622155641.25916-3-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Stephen Hemminger To: Stephen Hemminger Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 3A1844BE1 for ; Thu, 22 Jun 2017 18:05:43 +0200 (CEST) In-Reply-To: <20170622155641.25916-3-stephen@networkplumber.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 22/06/2017 17:56, Stephen Hemminger: > In some environments, the PCI domain can be larger than 16 bits. > For example, a PCI device passed through in Azure gets a synthetic domain > id which is internally generated based on GUID. The PCI standard does > not restrict domain to be 16 bits. > > This change breaks ABI for API's that expose PCI address structure. > > Signed-off-by: Stephen Hemminger > --- [...] > --- a/lib/librte_eal/common/include/rte_pci.h > +++ b/lib/librte_eal/common/include/rte_pci.h > @@ -63,7 +63,7 @@ const char *pci_get_sysfs_path(void); > > /** Formatting string for PCI device identifier: Ex: 0000:00:01.0 */ > #define PCI_PRI_FMT "%.4" PRIx16 ":%.2" PRIx8 ":%.2" PRIx8 ".%" PRIx8 > -#define PCI_PRI_STR_SIZE sizeof("XXXX:XX:XX.X") > +#define PCI_PRI_STR_SIZE sizeof("XXXXXXXX:XX:XX.X") I think you need to change PCI_PRI_FMT accordingly.