From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Roland Dreier <roland@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: mellanox mlx4_core and SR-IOV
Date: Thu, 2 Aug 2012 00:08:02 +0200 [thread overview]
Message-ID: <20120801220802.GP5470@ics.muni.cz> (raw)
In-Reply-To: <CAE9FiQWmgyirjjCwn54PkAsfvWxZSY5RhRVDkhhbK7E0NPzqaw@mail.gmail.com>
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).
so it seems, that pic=nocsr is a must now.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2012-08-01 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120801133835.GH5470@ics.muni.cz>
[not found] ` <CAG4TOxONLJnBaY7N5x7Kfi+dwCb507QPqX9s_Wuef10+RzM=AQ@mail.gmail.com>
2012-08-01 18:29 ` mellanox mlx4_core and SR-IOV Yinghai Lu
2012-08-01 20:28 ` Lukas Hejtmanek
2012-08-01 21:27 ` Yinghai Lu
2012-08-01 21:50 ` Lukas Hejtmanek
2012-08-01 20:56 ` Lukas Hejtmanek
2012-08-01 21:32 ` Yinghai Lu
2012-08-01 22:08 ` Lukas Hejtmanek [this message]
2012-08-01 23:36 ` Yinghai Lu
2012-08-03 8:33 ` Lukas Hejtmanek
2012-08-03 16:41 ` Yinghai Lu
2012-08-10 18:51 ` Chris Friesen
2012-08-10 22:34 ` Lukas Hejtmanek
2012-08-03 13:49 Konrad Wilk
2012-08-05 8:05 ` Lukas Hejtmanek
2012-08-06 14:07 ` Konrad Rzeszutek Wilk
2012-08-06 15:10 ` Lukas Hejtmanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120801220802.GP5470@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=roland@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).