linux-kernel - Re: [kvm-devel] [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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 12 Dec 2007 00:14:42 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	kvm-devel@...ts.sourceforge.net
Cc:	Avi Kivity <avi@...ranet.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] [RFC] Proposed new directory layout for kvm and	virtualization

On Tuesday 11 December 2007, Avi Kivity wrote:
> Heiko Carstens wrote:
> > On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
> >
> >>  arch/*/kvm/   arch dependent kvm code
> >>     
> >
> > Maybe arch/*/virt/ ? No need to add an own directory for each hypervisor.
> >
> There will be several kvm files in that directory for x86. If you have 
> just one file, I guess arch/*/virt/kvm.c is okay.

In that case, even arch/*/{mm,kernel}/kvm.c would work fine, as long as you
only want to support one hypervisor, or a small set of small files, there
is no need to have even have a virt directory.

However, if you want to have symmetry across the architectures, I think
arch/*/kvm/ works out best, along the lines of 
arch/*/{perfmon,crypto,xen,power}. Neither of these is particularly large,
but arch/* is typically not that crowded either.

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