mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Wilk" <davidwilk@gmail.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Chris Wright" <chrisw@sous-sol.org>, "Greg KH" <greg@kroah.com>,
	"Marcelo Tosatti" <marcelo.tosatti@cyclades.com>,
	stable@kernel.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [stable] 2.6.16.6 breaks java... sort of
Date: Wed, 26 Apr 2006 15:40:11 -0600	[thread overview]
Message-ID: <a4403ff60604261440u22b7e4c9k5be1a14e2f41e1e6@mail.gmail.com> (raw)
In-Reply-To: <p73fyk09ayc.fsf@bragg.suse.de>

In defense of having that option available, this was not a case where
the user was deliberately trying to set that option, but rather that
it somehow got set accidentally (still a bit of a mystery as I was not
modifying configs at the time).

On 26 Apr 2006 07:12:43 +0200, Andi Kleen <ak@suse.de> wrote:
> "David Wilk" <davidwilk@gmail.com> writes:
>
> > Ok, I think I need to apologize to everyone here.  I have found the
> > problem, and it is not with your patch, Hugh.  For some reason, the
> > config for my 2.6.16.7 source tree had a 1G/3G user/kernel split
> > configured.  This is very bizaar as I copy my .config from tree to
> > tree to avoid any changes in the configuration of my test kernels.
>
> This just shows this dreaded VMSPLIT config was a bad idea in the first
> place. There was a reason we didn't have it for such a long time (too
> many users get it wrong) and such occurrences just show again that this
> is still true.
>
> IMHO it would be best to just remove that option again and require
> users who really want to change this to patch their kernels again.
>
> At the very least it should be probably made dependent on CONFIG_EMBEDDED.
>
> -Andi
>
> Mark VMSPLIT EMBEDDED
>
> Too many users get it wrong.
>
> Signed-off-by: Andi Kleen <ak@suse.de>
>
> Index: linux/arch/i386/Kconfig
> ===================================================================
> --- linux.orig/arch/i386/Kconfig
> +++ linux/arch/i386/Kconfig
> @@ -466,7 +466,7 @@ endchoice
>
>  choice
>         depends on EXPERIMENTAL && !X86_PAE
> -       prompt "Memory split"
> +       prompt "Memory split" if EMBEDDED
>         default VMSPLIT_3G
>         help
>           Select the desired split between kernel and user memory.
>

      parent reply	other threads:[~2006-04-26 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4403ff60604191152u5a71e70fr9f54c104a654fc99@mail.gmail.com>
2006-04-19 19:28 ` Greg KH
2006-04-19 19:57   ` Hugh Dickins
2006-04-20 16:24     ` Hugh Dickins
2006-04-20 17:10       ` David Wilk
2006-04-21 19:08       ` David Wilk
2006-04-21 19:27         ` Chris Wright
2006-04-21 20:43           ` David Wilk
2006-04-21 21:56           ` David Wilk
2006-04-23 12:41             ` Hugh Dickins
2006-04-24 20:59               ` David Wilk
2006-04-25 17:51                 ` Hugh Dickins
2006-04-25 18:08                 ` David Wilk
2006-04-25 18:28                   ` Hugh Dickins
2006-04-26  5:12                   ` Andi Kleen
2006-04-26  8:03                     ` Adrian Bunk
2006-04-26 21:40                     ` David Wilk [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=a4403ff60604261440u22b7e4c9k5be1a14e2f41e1e6@mail.gmail.com \
    --to=davidwilk@gmail.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=stable@kernel.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

all inboxes | Powered by JetHome®