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  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:	Sun, 7 Dec 2014 17:05:06 +0000
From:	Yuval Mintz <>
To:	Eli Cohen <>,
	"" <>,
	David Miller <>
CC:	linux-pci <>,
	netdev <>,
	"" <>,
	"" <>,
	Eli Cohen <>,
	Donald Dutile <>
Subject: RE: [PATCH RFC] pci: Control whether VFs are probed on

>This can save host side resource usage by VF instances which would be
>eventually probed to VMs.

>Use a parameter to pci_enable_sriov to control that policy, and modify
>all current callers such that they retain the same functionality.

What's the end-game here? How eventually would this be controlled?

>Use a one shot flag on struct pci_device which is cleared after the
>first probe is ignored so subsequent attempts go through.

Does a one-shot flag suffice? E.g., consider assigning a VF to VM and
than shutting down the VM. Assuming this feature is disabled,
the VF didn't appear on the hypervisor prior to the assignment but
will appear after its shutdown.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists