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 AF354A10DA for ; Thu, 1 Aug 2019 09:15:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 89C8C1C1BD; Thu, 1 Aug 2019 09:15:34 +0200 (CEST) Received: from mail-vk1-f172.google.com (mail-vk1-f172.google.com [209.85.221.172]) by dpdk.org (Postfix) with ESMTP id 0A6851C1B6 for ; Thu, 1 Aug 2019 09:15:33 +0200 (CEST) Received: by mail-vk1-f172.google.com with SMTP id w186so5939357vkd.11 for ; Thu, 01 Aug 2019 00:15:32 -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=EcRJqaPRYq+SNk+RwD1J99PwyBul3tL7n3snRzRZm2M=; b=nzlfDQW+Ap7AAnzIMxxIbfy5JGoVCQbX1aKnSISkyUwCHtygiLp7O75VENp2uI9CQc 4/uRLmMzP+FTqgAZ5lrSRmbKZNxmyOafJ0wqmRn08dDrCHpZDZncRp5tPxgWMEfnwDGP meDkq2o0vdVSLm5THyhPYmhVmVFQPexjXgNbGH2qZyNxk293CymwQpYy+gnR9XYiDteb QtHT1kqZsUZuU/ccLWWG9ePKIrPjBCXAdikZFju2MkFtNpDbA7Ve6bQV8VCwHTi+atHk tzRCc618OvaoR6wBrw6sE5hxP5CNtPqUwAPOJOhF5QOiwhOkijfH4tKHyfrxtba00OW6 BICw== X-Gm-Message-State: APjAAAVbULeK0RCLoUr/terTNAmD8mqQiFgg7yFhdK2DAoAsZj2ZeXoO ki+z/WUrzyZKrE7Pqv9GhLkyxBh1uA13WGDmQqDYcA== X-Google-Smtp-Source: APXvYqw2s4+YLVwDIb7lR3Cij6pbDWVzRMZlch3xEjXcx7E1ejJMiB38NUNoRPHaW8nThzM87wu2nD5vF4VhV8noYn0= X-Received: by 2002:a1f:1185:: with SMTP id 127mr15954769vkr.85.1564643732407; Thu, 01 Aug 2019 00:15:32 -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 09:15:21 +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 7:25 AM Takeshi T Yoshimura wrote: > Okay. I should have set the --log-level=lib.*:debug. Here is the log. > > Starting SPDK v19.10-pre / DPDK 19.08.0-rc3 initialization... > [ DPDK EAL parameters: identify --no-shconf -c 0x1 -n 1 -m 0 --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6 --log-level=lib.*:debug --base-virtaddr=0x200000000000 --match-allocations --file-prefix=spdk_pid159692 ] [snip] > EAL: No shared files mode enabled, IPC will be disabled > EAL: No shared files mode enabled, IPC is disabled > EAL: VFIO PCI modules not loaded EAL thinks that vfio kmod is not loaded at this point. > EAL: Bus pci wants IOVA as 'DC' We see no log here for the devices that are used later. - Are the (below) devices bound to vfio-pci or any other kmod at this point of the init? - Is the spdk_nvme driver loaded at this point? - I suppose forcing --iova-mode=pa resolves the issue, but can you confirm this? > EAL: Buses did not request a specific IOVA mode. > EAL: IOMMU is available, selecting IOVA as VA mode. > EAL: Module /sys/module/rte_kni not found! error 2 (No such file or directory) > EAL: Selected IOVA mode 'VA' [snip] > EAL: PCI device 0000:01:00.0 on NUMA socket 0 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0000:01:00.0 cannot be used > EAL: PCI device 0003:01:00.0 on NUMA socket 0 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0003:01:00.0 cannot be used > EAL: PCI device 0030:01:00.0 on NUMA socket 8 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0030:01:00.0 cannot be used > No NVMe controllers found. -- David Marchand