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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 2BB47C433FF for ; Thu, 1 Aug 2019 09:46:59 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id DCC0020657 for ; Thu, 1 Aug 2019 09:46:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DCC0020657 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 594831C1D1; Thu, 1 Aug 2019 11:46:57 +0200 (CEST) Received: from mail-ua1-f67.google.com (mail-ua1-f67.google.com [209.85.222.67]) by dpdk.org (Postfix) with ESMTP id 4FFF41C1C6 for ; Thu, 1 Aug 2019 11:46:56 +0200 (CEST) Received: by mail-ua1-f67.google.com with SMTP id 34so28148869uar.8 for ; Thu, 01 Aug 2019 02:46:56 -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=rrvbWV/ylT59dOczThwHpPZS59fH57eMvl0G0/zZSNI=; b=nVv689lfPmOcu4IcEi7y4oPHA3xdhuUdjGstorh6d4KoA8MFIHfo1zA9bDkWo3pP5R 6O9YFPftZK+8/YNTkn28+dBi796ntYSRlYcQmULjAJvZMcb292deJduDlf95UHezraBP oduLIrH9tqLOp42kmEIMtBDpqjiLPrWDEPPaPaiZctKen9zhf98hmwoKTCvh57Mq/GEJ kBp97UkJOR26Ays6IUooerQ38iubnHJTxdcs72NiqsUFvR9VSil9mXL3T++X+BqUqMXX m0fp++aclnMaEEeo2T9a+2h1Z+TBqvoH9VSE4HnECYYyGNXYhpDYMJtSfOoWMVcxPK3g t5Ug== X-Gm-Message-State: APjAAAUPDlM9mRJD8DnIR7zw8IhhWk3fyHe3aAKSh1lw1zXw+H9o85Xz N5xrYHh1JMRSYxShML6pbKFvcfgCmFoKWQ7YOVNlaw== X-Google-Smtp-Source: APXvYqy3WTeD2CYca05+EI0pDk6dBrji1xkaHLglzPJdDfhWfScsiMzPL/yJmP/yBVIaFZ1KELBK7yztozRft3yqW9M= X-Received: by 2002:ab0:6198:: with SMTP id h24mr17408702uan.41.1564652815521; Thu, 01 Aug 2019 02:46:55 -0700 (PDT) MIME-Version: 1.0 References: <20190731033523.2482-1-tyos@jp.ibm.com> In-Reply-To: From: David Marchand Date: Thu, 1 Aug 2019 11:46:44 +0200 Message-ID: To: Takeshi T Yoshimura Cc: dev , David Christensen 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 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