mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: mlord@pobox.com, axboe@suse.de, sam@ravnborg.org,
	zippel@linux-m68k.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: VMPLIT question
Date: Sat, 12 Aug 2006 12:16:19 -0700	[thread overview]
Message-ID: <20060812191619.GE4919@us.ibm.com> (raw)
In-Reply-To: <1155393875.7574.88.camel@localhost.localdomain>

On 12.08.2006 [07:44:35 -0700], Dave Hansen wrote:
> On Fri, 2006-08-11 at 22:27 -0700, Nishanth Aravamudan wrote:
> > While building a newer kernel for a server (which had been running
> > 2.6.12 or so), I spent some time looking for how to set the VMSPLIT
> > .config options. I searched in menuconfig for VMSPLIT and was given a
> > few responses, all similar to this:
> > 
> >   â?????? Symbol: VMSPLIT_3G [=n]
> >   â?????? Prompt: 3G/1G user/kernel split
> >   â??????   Defined at arch/i386/Kconfig:488
> >   â??????   Depends on: <choice>             
> > 
> > Since depending on "<choice>" is less than helpful, I did an rgrep and
> > found what it actually depends on:
> > 
> >   depends on EXPERIMENTAL && !X86_PAE
> >   prompt "Memory split" if EMBEDDED
> >   default VMSPLIT_3G
> > 
> > and was able to determine that I needed the patch recently submitted by
> > Dave Hansen to enable VMSPLIT for highmem kernels. Is there a reason
> > that menuconfig is not able to tell me this, i.e. this is a known
> > limitation of the choice syntax?
> 
> You need to ask for help with the high-level option, not the actual
> "choice":

The "high-level option" being ...? What did you search for in menuconfig
to get the following? And, in any case, how is it useful to return a
"(null)" symbol name?

>   ??? Symbol: (null) [=y]                                                                         ???
>   ??? Prompt: Memory split                                                                        ???
>   ???   Defined at arch/i386/Kconfig:494                                                          ???
>   ???   Depends on: EXPERIMENTAL && !X86_PAE && EMBEDDED                                          ???
>   ???   Location:                                                                                 ???
>   ???     -> Processor type and features                                                          ???
>   ???   Selected by: EXPERIMENTAL && !X86_PAE && EMBEDDED && m                                    ???

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center

  parent reply	other threads:[~2006-08-12 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12  5:27 Nishanth Aravamudan
     [not found] ` <1155393875.7574.88.camel@localhost.localdomain>
2006-08-12 19:16   ` Nishanth Aravamudan [this message]
2006-08-14 16:59     ` Dave Hansen
2006-08-14 17:07       ` Nishanth Aravamudan
2006-08-14 17:12         ` Sam Ravnborg

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=20060812191619.GE4919@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=axboe@suse.de \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.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®