From: Andi Kleen <ak@suse.de>
To: Charles N Wyble <charles@thewybles.com>
Cc: virtualization@lists.linux-foundation.org,
Chris Wright <chrisw@sous-sol.org>,
Anthony Liguori <aliguori@us.ibm.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental.
Date: Tue, 18 Sep 2007 22:20:26 +0200 [thread overview]
Message-ID: <200709182220.27311.ak@suse.de> (raw)
In-Reply-To: <46F02F50.5000001@thewybles.com>
> Why is making something default y a bad idea?
> Those most likely to care can turn it off. Is there a harmful effect
> from leaving it on if its not being used?
Running yes "" | make oldconfig to upgrade kernel configs is standard practice
and you definitely don't want to have all kinds of random new unnecessary features
be turned on then.
Besides paravirt by itself is pretty useless; you need typically quite
complex other options set to do any meaningfull virtualization.
The only reason to use default y is in options that are not user visible
and have a reasonable default or things that cause direct boot failures
when upgrading old configurations. That all doesn't apply here.
Besides it's bad taste and taste is very important.
-Andi
next prev parent reply other threads:[~2007-09-18 20:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 5:17 [PATCH 1/3] Normalize config options for guest support Rusty Russell
2007-09-14 5:18 ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Rusty Russell
2007-09-14 5:18 ` Rusty Russell
2007-09-14 5:21 ` [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental Rusty Russell
2007-09-18 10:57 ` Andi Kleen
2007-09-18 10:57 ` Andi Kleen
2007-09-18 20:04 ` Charles N Wyble
2007-09-18 20:20 ` Andi Kleen
2007-09-18 20:20 ` Andi Kleen [this message]
2007-09-18 20:27 ` Charles N Wyble
2007-09-18 20:41 ` Andi Kleen
2007-09-18 20:41 ` Andi Kleen
2007-09-20 15:45 ` Satyam Sharma
2007-09-20 15:45 ` Satyam Sharma
2007-09-20 16:09 ` Charles N Wyble
2007-09-20 16:09 ` Charles N Wyble
2007-09-20 16:47 ` Satyam Sharma
2007-09-20 16:47 ` Satyam Sharma
2007-09-18 20:27 ` Charles N Wyble
2007-09-18 20:04 ` Charles N Wyble
2007-09-18 21:34 ` Rusty Russell
2007-09-18 21:52 ` Andi Kleen
2007-09-18 21:52 ` Andi Kleen
2007-09-19 1:53 ` Rusty Russell
2007-09-19 1:53 ` Rusty Russell
2007-09-19 3:59 ` Jeremy Fitzhardinge
2007-09-19 10:43 ` Ian Campbell
2007-09-19 10:43 ` Ian Campbell
2007-09-19 3:59 ` Jeremy Fitzhardinge
2007-09-18 21:34 ` Rusty Russell
2007-09-14 5:21 ` Rusty Russell
2007-09-14 16:19 ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Randy Dunlap
2007-09-14 16:19 ` Randy Dunlap
2007-09-14 20:01 ` Jan Engelhardt
2007-09-14 20:01 ` Jan Engelhardt
2007-09-15 3:05 ` Rusty Russell
2007-09-15 8:49 ` Alexey Eremenko
2007-09-16 7:43 ` Rusty Russell
2007-09-16 7:43 ` Rusty Russell
2007-09-16 14:56 ` Jeremy Fitzhardinge
2007-09-16 14:56 ` Jeremy Fitzhardinge
2007-09-17 19:31 ` Zachary Amsden
2007-09-17 23:30 ` Charles N Wyble
2007-09-17 23:30 ` Charles N Wyble
2007-09-18 0:18 ` Jeremy Fitzhardinge
2007-09-18 20:11 ` Charles N Wyble
2007-09-19 9:38 ` Alexey Eremenko
2007-09-19 9:38 ` Alexey Eremenko
2007-09-18 20:11 ` Charles N Wyble
2007-09-18 0:18 ` Jeremy Fitzhardinge
2007-09-17 19:31 ` Zachary Amsden
2007-09-15 8:49 ` Alexey Eremenko
2007-09-15 3:05 ` 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=200709182220.27311.ak@suse.de \
--to=ak@suse.de \
--cc=aliguori@us.ibm.com \
--cc=charles@thewybles.com \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 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.