linux-kernel - mellanox mlx4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120801133835.GH5470@ics.muni.cz>
Date:	Wed, 1 Aug 2012 15:38:35 +0200
From:	Lukas Hejtmanek <xhejtman@....muni.cz>
To:	roland@...nel.org
Cc:	linux-kernel@...r.kernel.org
Subject: mellanox mlx4_core and SR-IOV

Hello,

I tried to use SR-IOV virtualizaton for Mellanox ConnectX2 card with
mlx4_core driver with kernel 3.5.0. I built firware for the IB card with
sriov_en = true, lspci shows:
02:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s
- IB QDR / 10GigE] (rev b0)
        Subsystem: Super Micro Computer Inc Device 0048
        Flags: bus master, fast devsel, latency 0, IRQ 24
        Memory at fbd00000 (64-bit, non-prefetchable) [size=1M]
        Memory at f8800000 (64-bit, prefetchable) [size=8M]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] Vital Product Data
        Capabilities: [9c] MSI-X: Enable+ Count=128 Masked-
        Capabilities: [60] Express Endpoint, MSI 00
        Capabilities: [100] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [148] Device Serial Number 00-25-90-ff-ff-28-09-08
        Capabilities: [108] Single Root I/O Virtualization (SR-IOV)
        Kernel driver in use: mlx4_core

however, the driver complains:
[    3.558221] mlx4_core 0000:02:00.0: Enabling sriov with:4 vfs
[    3.558296] mlx4_core 0000:02:00.0: not enough MMIO resources for SR-IOV (nres: 0, iov->nres: 1)
[    3.558299] mlx4_core 0000:02:00.0: Failed to enable sriov,continuing without sriov enabled (err = -12).

Is there any workaround for this? Or the bug is in BIOS and without a proper
fix this is never gonna work? 

Perhaps, are there any persons more suitable for these kind of questions?

-- 
Lukáš Hejtmánek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/