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
| ||
|
Date: Fri, 23 Jul 2010 10:08:14 +0200 From: Stefan Assmann <sassmann@...hat.com> To: Casey Leedom <leedom@...lsio.com> CC: "Rose, Gregory V" <gregory.v.rose@...el.com>, David Miller <davem@...emloft.net>, shemminger@...tta.com, andy@...yhouse.net, harald@...hat.com, bhutchings@...arflare.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, gospo@...hat.com, "Duyck, Alexander H" <alexander.h.duyck@...el.com> Subject: Re: [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address On 23.07.2010 02:26, Casey Leedom wrote: > > Or you simply don't have the VF Driver loaded in the "Domain 0" Control OS. When we install the cxgb4 PF Driver with "num_vf=..." this enables the PCI-E SR-IOV Capabilities within the various PFs and the corresponding VF PCI Devices are instantiated and discovered by the Domain 0 Linux OS. But without a cxgb4vf VF Driver loaded, those devices just sit there . available for "Device Assignment" to VMs. > Just out of curiosity, how do you prevent the VF driver from getting loaded in the host? Except from blacklisting it. Stefan -- Stefan Assmann | Red Hat GmbH Software Engineer | Otto-Hahn-Strasse 20, 85609 Dornach | HR: Amtsgericht Muenchen HRB 153243 | GF: Brendan Lane, Charlie Peters, sassmann at redhat.com | Michael Cunningham, Charles Cachera -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists