[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQW84gjtX=_4guCBgcAJmkAGQ5ooFoj7C_29K7QK0s9qwA@mail.gmail.com>
Date: Wed, 1 Aug 2012 16:36:14 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Lukas Hejtmanek <xhejtman@....muni.cz>
Cc: Roland Dreier <roland@...nel.org>, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: mellanox mlx4_core and SR-IOV
On Wed, Aug 1, 2012 at 3:08 PM, Lukas Hejtmanek <xhejtman@....muni.cz> wrote:
> On Wed, Aug 01, 2012 at 02:32:17PM -0700, Yinghai Lu wrote:
>> yes, i knew that.
>>
>> one patch in my for-pci-next should address that.
>>
>> http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=patch;h=fcce563f868e296f46a2eeaa88d6959bcee26a2d
>
> this is probably only half-way. well mlx driver loads but it complains again
> on MMIO:
> [ 3.564844] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011)
> [ 3.564845] mlx4_core: Initializing 0000:02:00.0
> [ 3.564967] mlx4_core 0000:02:00.0: Enabling sriov with:4 vfs
> [ 3.565087] mlx4_core 0000:02:00.0: not enough MMIO resources for SR-IOV
> [ 3.565402] mlx4_core 0000:02:00.0: Failed to enable sriov,continuing
> without sriov enabled (err = -12).
yes, that is, it will make BAR2 has fallback resource again.
>
> so it seems, that pic=nocsr is a must now.
yes. Or you have bios provide SRIOV support or 64 bit resource in _CRS.
Yinghai
--
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/
Powered by blists - more mailing lists