From: Avi Kivity <avi@qumranet.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 17:52:30 +0200 [thread overview]
Message-ID: <475EB23E.1060002@qumranet.com> (raw)
In-Reply-To: <20071211151143.GA7751@osiris.boeblingen.de.ibm.com>
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
next prev parent reply other threads:[~2007-12-11 15:52 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
2007-12-11 15:11 ` Heiko Carstens
2007-12-11 15:52 ` Avi Kivity [this message]
2007-12-11 23:14 ` [kvm-devel] " 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=475EB23E.1060002@qumranet.com \
--to=avi@qumranet.com \
--cc=heiko.carstens@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