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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 6 Nov 2008 22:18:35 -0800
From:	Greg KH <greg@...ah.com>
To:	"Fischer, Anna" <anna.fischer@...com>
Cc:	H L <swdevyid@...oo.com>,
	"randy.dunlap@...cle.com" <randy.dunlap@...cle.com>,
	"grundler@...isc-linux.org" <grundler@...isc-linux.org>,
	"Chiang, Alexander" <achiang@...com>,
	"matthew@....cx" <matthew@....cx>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"rdreier@...co.com" <rdreier@...co.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
	"mingo@...e.hu" <mingo@...e.hu>
Subject: Re: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support

On Thu, Nov 06, 2008 at 09:35:57PM +0000, Fischer, Anna wrote:
> > Perhaps some of this could be hidden with a new bus type for these
> > kinds
> > of devices?  Or a "virtual" bus of pci devices that the original SR-IOV
> > device creates that corrispond to the individual virtual PCI devices?
> > If that were the case, then it might be a lot easier in the end.
> 
> I think a standard communication channel in Linux for SR-IOV devices
> would be a good start, and help to adopt the technology. Something
> like the virtual bus you are describing. It means that vendors do
> not need to write their own communication channel in the drivers.
> It would need to have well defined APIs though, as I guess that
> devices will have very different capabilities and hardware
> implementations for PFs and VFs, and so they might have very
> different events and information to propagate.

That would be good to standardize on.  Have patches?

thanks,

greg k-h
--
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