From: Avi Kivity <avi@qumranet.com>
To: Rusty Russell <rusty@rustcorp.com.au>
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>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option
Date: Fri, 20 Jul 2007 08:24:01 +0300 [thread overview]
Message-ID: <46A046F1.7040207@qumranet.com> (raw)
In-Reply-To: <1184905342.10380.263.camel@localhost.localdomain>
Rusty Russell wrote:
> Any objections?
>
> Rusty.
> ===
> Having KVM appear in the middle of "drivers" is kinda strange, and
> having it alone under a menu called "virtualization" doubly so.
>
> 1) Move the "Virtualization" menu into the arch-specific i386 and
> x86-64 Kconfig.
>
Virtualization is hardly x86 specific. How about moving it to
top-level, and having individual items disable themselves on archs they
don't apply to?
Otherwise we end up with $NARCH copies of that Kconfig, each slightly
different. The top-level entry can be made to depend on the archs that
actually have some virt capability, so as not to show empty an menu.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-07-20 5:24 UTC|newest]
Thread overview: 16+ 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 4:31 ` Alexey Eremenko
2007-07-20 5:24 ` Avi Kivity [this message]
2007-07-20 6:02 ` Rusty Russell
2007-07-20 6:10 ` Zachary Amsden
2007-07-20 6:10 ` Zachary Amsden
2007-07-20 14:09 ` Jeff Dike
2007-07-20 14:09 ` Jeff Dike
2007-07-20 6:02 ` Rusty Russell
2007-07-20 5:24 ` Avi Kivity
2007-07-21 15:49 ` Jan Engelhardt
2007-07-21 15:49 ` Jan Engelhardt
2007-07-23 5:09 ` Rusty Russell
2007-07-23 5:09 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2007-07-20 4:22 Rusty Russell
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=46A046F1.7040207@qumranet.com \
--to=avi@qumranet.com \
--cc=ak@muc.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.