netdev - Re: [PATCH v2 6/7] PCI: Make sure VF's driver get attached after PF's

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]

Date:	Mon, 20 May 2013 09:01:58 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Eliezer Tamir <eliezer.tamir@...ux.intel.com>
Cc:	Or Gerlitz <or.gerlitz@...il.com>,
	Greg Rose <gregory.v.rose@...el.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Gu Zheng <guz.fnst@...fujitsu.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alexander Duyck <alexander.h.duyck@...el.com>,
	Yan Burman <yanb@...lanox.com>,
	Sathya Perla <Sathya.Perla@...lex.com>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 6/7] PCI: Make sure VF's driver get attached after PF's

On Mon, May 20, 2013 at 5:58 AM, Eliezer Tamir
<eliezer.tamir@...ux.intel.com> wrote:
>>
> Maybe do the following:
> 1. split the VF PCI IDs into a separate PCI_ID device table.
> 2. have two pci_driver structs, one for all of the PF IDS and one with the
> VF IDS.
> 3. only register the first pci_driver struct from mlx4_init().
> 4. register the one for the VFs once your PFs are all up and ready.

that may help booting path that have driver built-in, or first time
load driver path.

For driver already loaded, and hotadd path, the problem is still there.

Yinghai
--
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