| 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: Thu, 7 Apr 2011 05:34:14 -0700 From: <Ajit.Khaparde@...lex.Com> To: <bhutchings@...arflare.com> CC: <netdev@...r.kernel.org> Subject: RE: [PATCH net-next 2/5] be2net: use common method to check for sriov function type ________________________________________ > From: Ben Hutchings [bhutchings@...arflare.com] > Sent: Thursday, April 07, 2011 3:14 AM > To: Khaparde, Ajit > Cc: netdev@...r.kernel.org > Subject: Re: [PATCH net-next 2/5] be2net: use common method to check for sriov function type > On Wed, 2011-04-06 at 23:08 -0500, Ajit Khaparde wrote: >> Lancer and BE can both use SLI_INTF_REG to check a VF or a PF. > [...] > This seems pretty unreliable (both in the previous and the current > version). You cannot rely on the whole of PCI config space being mapped > to a VM guest. KVM certainly didn't do this when I used PCI pass- > through. That's interesting. I have been using the new method for a while now. And the older one has worked pretty well for a long time. Can you give some details about the adapter used? Let's start with the firmware version, lspci output. > Ben. > -- > Ben Hutchings, Senior Software Engineer, Solarflare > Not speaking for my employer; that's the marketing department's job. > They asked us to note that Solarflare product names are trademarked.-- 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
Powered by blists - more mailing lists