From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753910AbXLKNqp (ORCPT ); Tue, 11 Dec 2007 08:46:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751960AbXLKNqi (ORCPT ); Tue, 11 Dec 2007 08:46:38 -0500 Received: from il.qumranet.com ([82.166.9.18]:38364 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751940AbXLKNqh (ORCPT ); Tue, 11 Dec 2007 08:46:37 -0500 Message-ID: <475E94BA.8060402@qumranet.com> Date: Tue, 11 Dec 2007 15:46:34 +0200 From: Avi Kivity User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Christian Borntraeger CC: linux-kernel , kvm-devel Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization References: <475E5CBB.9080608@qumranet.com> <200712111438.51142.borntraeger@de.ibm.com> In-Reply-To: <200712111438.51142.borntraeger@de.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization Date: Tue, 11 Dec 2007 15:46:34 +0200 Message-ID: <475E94BA.8060402@qumranet.com> References: <475E5CBB.9080608@qumranet.com> <200712111438.51142.borntraeger@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , linux-kernel To: Christian Borntraeger Return-path: In-Reply-To: <200712111438.51142.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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 ------------------------------------------------------------------------- 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