linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Konrad Wilk <konrad.wilk@oracle.com>
Cc: yinghai@kernel.org, linux-pci@vger.kernel.org, roland@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: mellanox mlx4_core and SR-IOV
Date: Sun, 5 Aug 2012 10:05:00 +0200	[thread overview]
Message-ID: <20120805080500.GH25979@ics.muni.cz> (raw)
In-Reply-To: <9f903175-4080-4016-b9f8-83e8615c110e@default>

Hi,

On Fri, Aug 03, 2012 at 06:49:59AM -0700, Konrad Wilk wrote:
> This looks like you are using PV PCI passthrough? If so, did you
> remember to use 'iommu=soft' to enable the Xen-SWIOTLB in your guest?
> And are you booting with more than 4GB? Or is less than 3GB (so that you have
> a nice gap in E820).

good catch. I forgot to pass swiotl=force for DomU in Xen. So now, it seems
that mlx4_core works, mlx4_en (ethernet part) works as well. Unfortunately,
the IB part does not. IB layer complains that SR-IOV is currently unsupported
(kernel 3.5.0). So no luck here so far. 

There is OFED stack directly from Mellanox, that seems to support SR-IOV even
for IB layer, but they have buildable sources only for RHEL/SLES kernels
(2.6.32) and even correcting the sources to get it compile with 3.5.0 does not
make things work. The driver complains about interrupts not working in Dom0 or
even without Xen hypervisor at all.

The only good point is, that I managed to convice Supermicro (board
manufacturer), that enabling SR-IOV in BIOS leads to BIOS lockup, they
confirmed it and maybe they provide BIOS upgrade.

Thanks all.

-- 
Lukáš Hejtmánek

  reply	other threads:[~2012-08-05  8:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 13:49 mellanox mlx4_core and SR-IOV Konrad Wilk
2012-08-05  8:05 ` Lukas Hejtmanek [this message]
2012-08-06 14:07   ` Konrad Rzeszutek Wilk
2012-08-06 15:10     ` Lukas Hejtmanek
     [not found] <20120801133835.GH5470@ics.muni.cz>
     [not found] ` <CAG4TOxONLJnBaY7N5x7Kfi+dwCb507QPqX9s_Wuef10+RzM=AQ@mail.gmail.com>
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
2012-08-03 16:41               ` Yinghai Lu
2012-08-10 18:51               ` Chris Friesen
2012-08-10 22:34                 ` 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=20120805080500.GH25979@ics.muni.cz \
    --to=xhejtman@ics.muni.cz \
    --cc=konrad.wilk@oracle.com \
    --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).