From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 94BF0A10DA for ; Fri, 2 Aug 2019 10:22:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8DF961C225; Fri, 2 Aug 2019 10:22:16 +0200 (CEST) Received: from mail-vs1-f68.google.com (mail-vs1-f68.google.com [209.85.217.68]) by dpdk.org (Postfix) with ESMTP id DAD941C212 for ; Fri, 2 Aug 2019 10:22:15 +0200 (CEST) Received: by mail-vs1-f68.google.com with SMTP id u3so50749555vsh.6 for ; Fri, 02 Aug 2019 01:22:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z33zA286VYRas2XxEhFI3QJWgq1XBqmeEZZc867qcvc=; b=gRS7pfeB3lehzCn32mQuVvpfFlTzucQelMOfX5Th2z7K8GBBZRr4P9vGNSSWh2iwYy +1cIaucrvr/3oaKcRN2NxFxO5StPB2a6oVbNY3KXrqXowdbHaa/WjDFpq4JsAkM3G28f t8jhnN8h8wuH3/01nX1r7JcQsnFP6ceWD7CZddD8S2pj+ITLiKktzIhgUcXOnlD7CpLt O3sZzlXvKzjO+4qis7Lv36MSi9pGM1uTExI+nXDSFoFyH5cK+XF1chyjio3HgWFdOP3O jhhYMsWj1UHvOx6uqevFAQ5ke6px2VFtnxDCMFmJxmIzEVV0SOvlX1DKaHBEhaB1lKOy 5Rqg== X-Gm-Message-State: APjAAAWkRNXvtEuGjziwhwLWqzLuLHEw3kvHERDu3h0zLK2VUDd1CSUR s6lgb0MI8/KmAPpazl43swsoeGs6YNKP6OkQLeu3dg== X-Google-Smtp-Source: APXvYqzAZF0ZQ8aeLgSZYGCw0kpSS84T9kKIHTJBXOmFdCGg+a8i/+muACfOnJuf5UI1QHDeQoc13qAE+ODzf7olHHY= X-Received: by 2002:a67:d81b:: with SMTP id e27mr82563849vsj.198.1564734135234; Fri, 02 Aug 2019 01:22:15 -0700 (PDT) MIME-Version: 1.0 References: <20190731033523.2482-1-tyos@jp.ibm.com> In-Reply-To: From: David Marchand Date: Fri, 2 Aug 2019 10:22:04 +0200 Message-ID: To: Takeshi T Yoshimura Cc: dev , David Christensen , "Burakov, Anatoly" , Thomas Monjalon Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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 Fri, Aug 2, 2019 at 10:09 AM Takeshi T Yoshimura wrote: > > -----David Marchand wrote: ----- > > >To: Takeshi T Yoshimura > >From: David Marchand > >Date: 08/01/2019 06:47PM > >Cc: dev , David Christensen > >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in > >ppc > > > >On Thu, Aug 1, 2019 at 10:46 AM Takeshi T Yoshimura > >wrote: > >> > >> > - Are the (below) devices bound to vfio-pci or any other kmod at > >this point of the init? > >> > >> Yes, vfio-pci is bound to 0030:01:00.0 in the log. > >> > >> > - Is the spdk_nvme driver loaded at this point? > >> > >> No, spdk just attempts to initialize dpdk at this point. > >> After the initialization finishes, spdk probes the nvme driver. > > > >Do you mean that spdk registers its drivers after rte_eal_init() has > >returned? > > > >Nothing should prevent from registering the drivers them before > >calling rte_eal_init(), did you try this? > >If the drivers are in the form of shared libraries (.so files), did > >you try to load them using the -d eal option? > > > > > >-- > >David Marchand > > > > > > SPDK apps have to call rte_eal_init() before registering drivers, > since the driver allocates DMA memory. Registering a driver before calling rte_eal_init is something that works most of the time. Not sure I get your point here. > Do I have to change existing apps and spdk core to workaround this issue to use new versions of dpdk? I understand this is a regression and I am looking at it. If we are too short for 19.08, then we can go with your workaround, but it needs a better commitlog. -- David Marchand