[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <475E94BA.8060402@qumranet.com>
Date: Tue, 11 Dec 2007 15:46:34 +0200
From: Avi Kivity <avi@...ranet.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
CC: linux-kernel <linux-kernel@...r.kernel.org>,
kvm-devel <kvm-devel@...ts.sourceforge.net>
Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization
Christian Borntraeger wrote:
> Am Dienstag, 11. Dezember 2007 schrieb Avi Kivity:
>
>> 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.
>>
>
> For completeness, where do we want to put the drivers?
> drivers/*, drivers/net/* etc.
> or
> drivers/kvm/* drivers/xen/* etc.
>
There's already drivers/virtio/ for kvm. If kvm-specific drivers come
up, we can place them in drivers/kvm/.
--
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/
Powered by blists - more mailing lists