linux-kernel - [RFC] Proposed new directory layout for kvm and virtualization

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

Message-ID: <475E5CBB.9080608@qumranet.com>
Date:	Tue, 11 Dec 2007 11:47:39 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
CC:	kvm-devel <kvm-devel@...ts.sourceforge.net>
Subject: [RFC] Proposed new directory layout for kvm and virtualization

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.

Comments, alternative suggestions welcome.

[This was foreshadowed about a year ago in 
http://lkml.org/lkml/2006/11/28/32, where the conclusion of the thread 
was to wait a year before making this change.  Quite an accurate 
prediction.]

-- 
error compiling committee.c: too many arguments to function

--
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/