public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 15:46:34 +0200	[thread overview]
Message-ID: <475E94BA.8060402@qumranet.com> (raw)
In-Reply-To: <200712111438.51142.borntraeger@de.ibm.com>

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


  reply	other threads:[~2007-12-11 13:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11  9:47 [RFC] Proposed new directory layout for kvm and virtualization Avi Kivity
2007-12-11 13:38 ` Christian Borntraeger
2007-12-11 13:46   ` Avi Kivity [this message]
2007-12-11 15:11 ` Heiko Carstens
2007-12-11 15:52   ` [kvm-devel] " Avi Kivity
2007-12-11 23:14     ` Arnd Bergmann
2007-12-13  8:33       ` Avi Kivity
2007-12-13 10:16         ` Carsten Otte
2007-12-11 16:10 ` Sam Ravnborg
2007-12-11 16:15   ` Avi Kivity
2007-12-11 17:37     ` Sam Ravnborg
2007-12-11 17:42       ` Avi Kivity
2007-12-11 18:26         ` [kvm-devel] " Hollis Blanchard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=475E94BA.8060402@qumranet.com \
    --to=avi@qumranet.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox