From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [RFC] KVM Source layout Proposal to accommodate new CPU architecture Date: Sat, 29 Sep 2007 23:06:51 +1000 Message-ID: <1191071211.26950.28.camel@localhost.localdomain> References: <42DFA526FC41B1429CE7279EF83C6BDC753A4E@pdsmsx415.ccr.corp.intel.com> <46FB7566.9030504@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Sam Ravnborg , "Zhang, Xiantao" , virtualization To: Avi Kivity Return-path: In-Reply-To: <46FB7566.9030504-atKUWr5tajBWk0Htik3J/w@public.gmane.org> 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 On Thu, 2007-09-27 at 11:18 +0200, Avi Kivity wrote: > The whole drivers/kvm/ thing was just a trick to get merged quickly. I > think the new layout should be something like > > virt/kvm/, include/linux/kvm*.h -> common code > virt/lguest/ -> the other hypervisor > virt/virtio/ -> shared I/O infrastructure > virt/ -> the CONFIG_VIRTIALIZATION menu > arch/x86/kvm/, include/asm-x86/ -> x86 specific code > arch/ia64/kvm/, include/asm-ia64/ -> ia64 specific code The problem with this separation is that module source cannot span directories (at least, not that I could find). This is why lguest went for "i386_" prefix for arch separation. Cheers, Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/