From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization Date: Tue, 11 Dec 2007 14:38:50 +0100 Message-ID: <200712111438.51142.borntraeger@de.ibm.com> References: <475E5CBB.9080608@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , linux-kernel To: Avi Kivity Return-path: In-Reply-To: <475E5CBB.9080608-atKUWr5tajBWk0Htik3J/w@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Am Dienstag, 11. Dezember 2007 schrieb Avi Kivity: > KVM is due to receive support for multiple architectures (ppc, ia64, and > s390, in addition to the existing x86), hopefully in time for the 2.6.25 > merge window. It is awkward to place the new arch support in > drivers/kvm/, so I'd like to propose the following new layout: > > virt/ top-level directory for hypervisors > virt/kvm/ kvm common code > virt/lguest/ the other hypervisor > arch/*/kvm/ arch dependent kvm code > include/linux/kvm.h arch independent interface > include/asm/kvm.h arch dependent interface > include/linux/kvm_para.h arch independent guest interface > include/asm/kvm_para.h arch dependent guest interface > > The include/ hierarchy is already in place; I'm including it for > completeness. For completeness, where do we want to put the drivers? drivers/*, drivers/net/* etc. or drivers/kvm/* drivers/xen/* etc. Christian? ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php