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-next>] [day] [month] [year] [list]
Date:	Wed, 20 Aug 2014 18:29:22 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Sreekanth Reddy <sreekanth.reddy@...gotech.com>
Cc:	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Christoph Hellwig <hch@....de>,
	Sathya Prakash <sathya.prakash@...gotech.com>,
	Nagalakshmi Nandigama <nagalakshmi.nandigama@...gotech.com>,
	boris.ostrovsky@...cle.com
Subject: Re: How to get the number of VFs assigned to the guests in XEN

On Wed, Aug 20, 2014 at 04:33:29PM +0530, Sreekanth Reddy wrote:
> HI,
> 
> 
> 
> For SRIOV support, currently in the KVM environment, mpt3sas driver can use
> the API pci_vfs_assigned() to know the number of VFs that are currently
> assigned to the running VMs. So that during the PF driver unload time, if
> the return value of this API is greater than zero the our driver won't call
> the pci_disable_sriov() to disable the VFs.
> 
> 
> 
> Now for the same purpose in XEN environment, is there any API similar to
> pci_vfs_assigned() which the low lever device driver can use to know 'the
> number of VFs that are currently assigned to the running VMs'. In XEN
> environment this API pci_vfs_assigned() will return always zero even though
> VFs are assigned to the running VMs.

Odd. It should return the same value. Are the devices binded to pci-back?

> 
> 
> 
> Regards,
> 
> Sreekanth
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ