[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1185167371.6344.135.camel@localhost.localdomain>
Date: Mon, 23 Jul 2007 15:09:31 +1000
From: Rusty Russell <rusty@...tcorp.com.au>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andi Kleen <ak@....de>, Jeremy Fitzhardinge <jeremy@...p.org>,
Zachary Amsden <zach@...are.com>,
Avi Kivity <avi@...ranet.com>,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH] Move KVM, paravirt, lguest, VMI and Xen under
arch-level Virtualization option
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists