From: Rusty Russell <rusty@rustcorp.com.au>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <ak@muc.de>, Jeremy Fitzhardinge <jeremy@goop.org>,
Zachary Amsden <zach@vmware.com>, Avi Kivity <avi@qumranet.com>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option
Date: Mon, 23 Jul 2007 15:09:31 +1000 [thread overview]
Message-ID: <1185167371.6344.135.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0707211748320.21737@fbirervta.pbzchgretzou.qr>
On Sat, 2007-07-21 at 17:49 +0200, Jan Engelhardt wrote:
> On Jul 20 2007 14:22, Rusty Russell wrote:
> >Subject: [PATCH] Move KVM, paravirt, lguest,
> > VMI and Xen under arch-level Virtualization option
> >
> >Any objections?
>
> Well btw, would it make sense to also rearrange the directory structure along
> with it, i.e.
>
> drivers/kvm => drivers/virt/kvm
> drivers/lguest => drivers/virt/lguest
> drivers/xen => drivers/virt/xen
>
> Then the full kconfig (with menuconfig,if,endif) can go to
> drivers/virt/Kconfig.
It would reduce clutter a little, but it'll never cover cases where the
arch is always virtualized. You could move VMI there, but UML, PowerPC,
S/390 won't be moving.
I still think people expect virtualization under CPU features, so archs
should include the virt Kconfig explicitly there (rather than it just
appearing deep in drivers/). At which point cut & pasting variations of
the CONFIG_VIRTUALIZATION option is probably as good as any other
solution, and far less work.
Cheers,
Rusty.
prev parent reply other threads:[~2007-07-23 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 4:22 [PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option Rusty Russell
2007-07-20 4:31 ` Alexey Eremenko
2007-07-20 5:24 ` Avi Kivity
2007-07-20 6:02 ` Rusty Russell
2007-07-20 6:10 ` Zachary Amsden
2007-07-20 14:09 ` Jeff Dike
2007-07-21 15:49 ` Jan Engelhardt
2007-07-23 5:09 ` Rusty Russell [this message]
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=1185167371.6344.135.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@muc.de \
--cc=avi@qumranet.com \
--cc=jengelh@computergmbh.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zach@vmware.com \
/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