linux-kernel - Re: [PATCH 0/13 v7] PCI: Linux kernel SR-IOV support

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4949B7CE.5010704@intel.com>
Date:	Thu, 18 Dec 2008 10:39:10 +0800
From:	"Zhao, Yu" <yu.zhao@...el.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Greg KH <greg@...ah.com>,
	"Rose, Gregory V" <gregory.v.rose@...el.com>,
	Jike Song <albcamus@...il.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"achiang@...com" <achiang@...com>,
	"bjorn.helgaas@...com" <bjorn.helgaas@...com>,
	"grundler@...isc-linux.org" <grundler@...isc-linux.org>,
	"mingo@...e.hu" <mingo@...e.hu>, "matthew@....cx" <matthew@....cx>,
	"randy.dunlap@...cle.com" <randy.dunlap@...cle.com>,
	"rdreier@...co.com" <rdreier@...co.com>,
	"horms@...ge.net.au" <horms@...ge.net.au>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"virtualization@...ts.linux-foundation.org" 
	<virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH 0/13 v7] PCI: Linux kernel SR-IOV support

Jesse Barnes wrote:
> On Wednesday, December 17, 2008 11:51 am Greg KH wrote:
>> On Wed, Dec 17, 2008 at 11:42:54AM -0800, Jesse Barnes wrote:
>>> I really don't want the SR-IOV stuff to sit out another merge cycle
>>> though... Arg.
>> Why, is there some rush to get it in?  As there is no in-kernel users of
>> it, I don't see the problem with postponing it until someone actually
>> needs it.
> 
> Well it *does* make development of SR-IOV drivers that much harder.  As you 
> know, out of tree development is a pain.  OTOH if any changes end up being 
> required, they can be done before the code is merged.

Yes, people write to me asking for the SR-IOV patch or update everyday 
-- I guess they don't want to let their competitors know they are 
working on it so they can't bring their questions up on the mailing list.

And I personally also have dozen of other patches related to PCI and KVM 
subsystems which depend on the SR-IOV change.

> Anyway, hopefully we won't have to worry about it because some driver will 
> come along soon that uses Yu's code. :)  If not, Yu might have to maintain a 
> separate git tree or something until the drivers are ready to be merged.
--
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/