Sam Ravnborg wrote: > On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote: > >> 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 >> > > The arch/*/dir shall use same dir-name as used > in top-level directory. >
Well, it isn't like that now (arch/x86/oprofile, etc.) > So use arch/*/virt/kvm/ if kvm really requires > a subdirectory of it own. Preferably not. > A handful of files named kvm* does not warrant their own > subdirectory IMO. > > We'll have 5-6 x86 specific files. Where do you suggest we place them? -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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 _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
