netdev - Re: [PATCH net-next V0 19/21] mlx4_core: Modify driver initialization flow to accommodate SRIOV for Ethernet

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL1RGDWsenbb6Z6pZtQ056itHgom08WryLJ-6=+okSh1xbgP=A@mail.gmail.com>
Date:	Mon, 5 Dec 2011 11:01:42 -0800
From:	Roland Dreier <roland@...estorage.com>
To:	Jack Morgenstein <jackm@....mellanox.co.il>
Cc:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>, davem@...emloft.net,
	netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
	liranl@...lanox.co.il
Subject: Re: [PATCH net-next V0 19/21] mlx4_core: Modify driver initialization
 flow to accommodate SRIOV for Ethernet

On Sun, Dec 4, 2011 at 6:29 AM, Jack Morgenstein
<jackm@....mellanox.co.il> wrote:
> If the kernel is not configured to support IOV, pci_enable_sriov will fail.
> Currently, we abort the device startup.  I can change this to simply continue
> without sriov enabled:

Agree... we definitely don't want drivers failing just because a
device has an SR-IOV
cap but the kernel isn't compiled with SR-IOV support.

 - R.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html