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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Dec 2007 17:52:30 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
CC:	kvm-devel <kvm-devel@...ts.sourceforge.net>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] [RFC] Proposed new directory layout for kvm and	virtualization

Heiko Carstens 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:
>> ...
>>  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.

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