From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [RFC] vfio: only map regions VFIO supports
Date: Fri, 10 Jul 2015 10:24:48 -0700
Message-ID: <20150710102448.263257d4@urahara>
References: <1436395131-11205-1-git-send-email-stephen@networkplumber.org>
 <533710CFB86FA344BFBF2D6802E60286046B663B@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: "Qiu, Michael" <michael.qiu@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com
 [209.85.192.174]) by dpdk.org (Postfix) with ESMTP id A2337C432
 for <dev@dpdk.org>; Fri, 10 Jul 2015 19:24:40 +0200 (CEST)
Received: by pdbqm3 with SMTP id qm3so43689420pdb.0
 for <dev@dpdk.org>; Fri, 10 Jul 2015 10:24:39 -0700 (PDT)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286046B663B@SHSMSX101.ccr.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Fri, 10 Jul 2015 07:54:10 +0000
"Qiu, Michael" <michael.qiu@intel.com> wrote:

> Hi, Stephen
> 
> This patch does not work for fm10k with vfio, see error below:
> 
> EAL: PCI device 0000:84:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:15a4 rte_pmd_fm10k
> EAL:   PCI memory mapped at 0x7f1980000000
> EAL: Trying to map BAR 2 that contains the MSI-X table. Trying offsets:
> 0000:0000, 1000:1000
> EAL:   PCI memory mapped at 0x7f1980401000
> EAL: pci_map_resource(): cannot mmap(105, 0x7f1980402000, 0x4000000,
> 0x0): Invalid argument (0xffffffffffffffff)
> EAL:   0000:84:00.0 mapping BAR4 failed: Invalid argument
> EAL: Error - exiting with code: 1
>   Cause: Requested device 0000:84:00.0 cannot be used

Yes. The patch doesn't solve the problem (but might be needed in some future weird hw).