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: Fri, 3 Aug 2012 10:33:44 +0200 [thread overview]
Message-ID: <20120803083344.GF25979@ics.muni.cz> (raw)
In-Reply-To: <CAE9FiQW84gjtX=_4guCBgcAJmkAGQ5ooFoj7C_29K7QK0s9qwA@mail.gmail.com>
On Wed, Aug 01, 2012 at 04:36:14PM -0700, Yinghai Lu wrote:
> > so it seems, that pic=nocsr is a must now.
>
> yes. Or you have bios provide SRIOV support or 64 bit resource in _CRS.
Well, I can use PCI passthrough in Xen now, however, it seems SR-IOV does not
work in case of Mellanox mlx4 driver.
With 3.5 stock kernel, I got this message in virtual domain:
[ 2.666623] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011)
[ 2.666635] mlx4_core: Initializing 0000:00:00.1
[ 2.666717] mlx4_core 0000:00:00.1: enabling device (0000 -> 0002)
[ 2.666975] mlx4_core 0000:00:00.1: Xen PCI mapped GSI0 to IRQ168
[ 2.667040] mlx4_core 0000:00:00.1: enabling bus mastering
[ 2.667184] mlx4_core 0000:00:00.1: Detected virtual function - running in slave mode
[ 2.667214] mlx4_core 0000:00:00.1: Sending reset
[ 2.667319] mlx4_core 0000:00:00.1: Sending vhcr0
[ 2.667886] mlx4_core 0000:00:00.1: HCA minimum page size:1
[ 2.668067] mlx4_core 0000:00:00.1: The host doesn't support eth interface
[ 2.668074] mlx4_core 0000:00:00.1: QUERY_FUNC_CAP command failed, aborting.
[ 2.668079] mlx4_core 0000:00:00.1: Failed to obtain slave caps
[ 2.668305] mlx4_core: probe of 0000:00:00.1 failed with error -93
not sure what does it mean.
I also tried OFED package from Mellanox which seems to have better SR-IOV
support (at least mlx4_ib does not complain that SR-IOV is not supported).
However, it does not work when SR-IOV enabled:
[13677.034266] mlx4_core 0000:02:00.0: Running in master mode
[13689.278238] mlx4_core 0000:02:00.0: command 0x31 timed out (go bit not cleared)
[13689.278324] mlx4_core 0000:02:00.0: NOP command failed to generate MSI-X interrupt IRQ 241).
[13689.278399] mlx4_core 0000:02:00.0: Trying again without MSI-X.
[13699.286473] mlx4_core 0000:02:00.0: command 0x31 timed out (go bit not cleared)
[13699.286557] mlx4_core 0000:02:00.0: NOP command failed to generate interrupt (IRQ 237), aborting.
[13699.286633] mlx4_core 0000:02:00.0: BIOS or ACPI interrupt routing problem?
[13701.406680] mlx4_core: probe of 0000:02:00.0 failed with error -16
if I disable SR-IOV mode for this driver, it works OK. Could the interrupt
problem be BIOS related? I.e., it won't work until I got BIOS which properly
supports SR-IOV with Mellanox card?
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2012-08-03 8:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 13:38 mellanox mlx4_core and SR-IOV Lukas Hejtmanek
2012-08-01 17:37 ` Roland Dreier
2012-08-01 18:29 ` 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
2012-08-01 23:36 ` Yinghai Lu
2012-08-03 8:33 ` Lukas Hejtmanek [this message]
2012-08-03 16:41 ` Yinghai Lu
2012-08-10 18:51 ` Chris Friesen
2012-08-10 22:34 ` Lukas Hejtmanek
-- strict thread matches above, loose matches on Subject: below --
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
2012-11-27 1:05 Zhangxiaofeng
[not found] ` <AE94C31276ACE14591CDCF7F6B4E699455547DBF-HvUXlCZMZtTDofk7SaG+FwK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2012-11-27 2:30 ` Jon Stanley
[not found] ` <CALY6xngZ2PTf6hiPcpQjaJDnGO=L9gMZg_h2d4S6MJx-+quUDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-27 4:54 ` Albert Strasheim
[not found] ` <CALfB72AHagg7GF2i2vuBw4_M0QHw-xkbdSXmuJKvynv-ZjLMow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-30 0:41 ` Zhangxiaofeng
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=20120803083344.GF25979@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.