linux-kernel - Re: [Pv-drivers] [PATCH 00/12] VMCI for Linux upstreaming

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]

Message-ID: <20121030162723.GA16135@kroah.com>
Date:	Tue, 30 Oct 2012 09:27:23 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dmitry Torokhov <dtor@...are.com>
Cc:	George Zhang <georgezhang@...are.com>, pv-drivers@...are.com,
	linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org
Subject: Re: [Pv-drivers] [PATCH 00/12] VMCI for Linux upstreaming

On Tue, Oct 30, 2012 at 09:18:07AM -0700, Dmitry Torokhov wrote:
> > > I think that even if we had a special directory for vmci having network
> > > drivers in Dave's realm and pvscsi in James's is best option, so the new
> > > directory would contain vmci and the balloon driver (vsock will go into
> > > net/).  Given that balloon is already in drivers/misc it looked like
> > > obvious place for VMCI as well.
> > 
> > I agree that the individual drivers should go in the subsystem area,
> > it's this "hypervisor bus core" type code that I'm questioning.  Right
> > now every hypervisor is putting that logic in a different place in the
> > kernel, having some consistency here would be nice.
> 
> Hmm, I wonder if miscellaneous and core hypervisor drivers should end
> up in drivers/platform:
> 
> 	drivers/platform/hyperv
> 	drivers/platform/olpc
> 	drivers/platform/vmware
> 	drivers/platform/xen
> 	drivers/platform/x86

That makes sense to me, nice.

> But really we'd like to get VMCI into mainline first and move to a new
> place later if such a better place is found.

Heh, no one wants to fight for something to help everyone out, they just
want their own code accepted :)

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/