public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 11:47:39 +0200	[thread overview]
Message-ID: <475E5CBB.9080608@qumranet.com> (raw)

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.

Comments, alternative suggestions welcome.

[This was foreshadowed about a year ago in 
http://lkml.org/lkml/2006/11/28/32, where the conclusion of the thread 
was to wait a year before making this change.  Quite an accurate 
prediction.]

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

             reply	other threads:[~2007-12-11  9:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11  9:47 Avi Kivity [this message]
     [not found] ` <475E5CBB.9080608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-11 13:38   ` [RFC] Proposed new directory layout for kvm and virtualization Christian Borntraeger
     [not found]     ` <200712111438.51142.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-12-11 13:46       ` Avi Kivity
2007-12-11 15:11 ` Heiko Carstens
     [not found]   ` <20071211151143.GA7751-Pmgahw53EmNLmI7Nx2oIsGnsbthNF6/HVpNB7YpNyf8@public.gmane.org>
2007-12-11 15:52     ` Avi Kivity
     [not found]       ` <475EB23E.1060002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-11 23:14         ` Arnd Bergmann
     [not found]           ` <200712120014.43314.arnd-r2nGTMty4D4@public.gmane.org>
2007-12-13  8:33             ` Avi Kivity
2007-12-13 10:16               ` [kvm-devel] " Carsten Otte
2007-12-11 16:10 ` Sam Ravnborg
2007-12-11 16:15   ` Avi Kivity
     [not found]     ` <475EB7AC.9040903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-11 17:37       ` Sam Ravnborg
     [not found]         ` <20071211173717.GA26368-QabhHTsIXMSnlFQ6Q1D1Y0B+6BGkLq7r@public.gmane.org>
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=475E5CBB.9080608@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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