From: "Sergio Luis" <sergio@uece.br>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Parag Warudkar" <parag.warudkar@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"akpm@osdl.org" <akpm@osdl.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Arjan van de Ven" <arjan@infradead.org>,
"Dave Jones" <davej@redhat.com>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED
Date: Mon, 5 May 2008 15:36:45 -0300 [thread overview]
Message-ID: <ce0170d90805051136w2f016c15p575623d33c220ddf@mail.gmail.com> (raw)
In-Reply-To: <20080505182427.GA2025@uranus.ravnborg.org>
On Mon, May 5, 2008 at 3:24 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Mon, May 05, 2008 at 07:15:01PM +0200, Ingo Molnar wrote:
> >
> > * Parag Warudkar <parag.warudkar@gmail.com> wrote:
> >
> > > sched-devel does not boot on my machine - stops right after PCI: Not
> > > using mmconfig.
> > >
> > > Here is my config for sched-devel - I did a echo "n" | make oldconfig
> > > after copying over the previous config file BTW. Should I try
> > > disabling things in config? What's most likely to break boot? (Seems
> > > likes there are a lot of significant changes in there.)
> >
> > every config is supposed to work, but in general you should pick the
> > defaults instead of saying 'n' to all questions. As long as every
> > question can be answered with an 'enter', this should work:
> >
> > make oldconfig < /dev/null
> >
> > this non-interactive 'make oldconfig' will hang with the kconfig tool
> > looping infinitely if there's any numeric question that cannot be
> > answered via 'enter'.
> >
> > This is a many years old kconfig bug that is frequently hacked around in
> > distro kernel packages but which has been ignored upstream - i've
> > attached Fedora's nonint_oldconfig patch from Dave Jones below. (maybe
> > Arjan wrote it originally?)
>
> In latest kbuild.git I've added a new feature.
>
> make K=.config alldefconfig
>
> would give you eaxtly what you request here.
> K= is used to say where to locate the base-configuration.
>
> The above will give you a configuration based on your old configuration
> with all new options set to default values.
>
> That could maybe be more intuitive but when you consider it you
> could have your base config in many different places.
> Like /boot/config-xxx, /proc/config.gz etc.
> So allowing the user to specify the base config with K= seems
> like an acceptable solution.
Can I specify /proc/config.gz (gzipped) in the K parameter?
-sergio
>
> Current version in kbuild.git is broken with respect to make O=...
> builds but that will be fixed in an hour or so.
>
> redhat has the added possibility to list new symbols.
> This is not yet included in mainline.
> Not that it is difficult - I just need to decide where/how to do it.
>
> Sam
>
next prev parent reply other threads:[~2008-05-05 18:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 0:42 Parag Warudkar
2008-05-04 9:24 ` Ingo Molnar
2008-05-05 15:14 ` Parag Warudkar
2008-05-05 17:15 ` Ingo Molnar
2008-05-05 18:24 ` Sam Ravnborg
2008-05-05 18:36 ` Sergio Luis [this message]
2008-05-05 18:45 ` Ingo Molnar
2008-05-05 19:49 ` [PATCH] kconfig: add support for stdin (make K=- ...) Sam Ravnborg
2008-05-06 3:51 ` Oleg Verych
2008-05-05 19:05 ` [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED Sam Ravnborg
2008-05-05 18:42 ` Ingo Molnar
2008-05-05 19:01 ` Sam Ravnborg
2008-05-05 19:56 ` Arjan van de Ven
2008-05-05 20:27 ` Ingo Molnar
2008-05-05 20:48 ` Linus Torvalds
2008-05-05 21:05 ` Ingo Molnar
2008-05-05 21:40 ` Parag Warudkar
2008-05-25 19:30 ` Roman Zippel
2008-05-05 17:21 ` Ingo Molnar
2008-05-05 17:33 ` Jesse Barnes
2008-05-05 18:36 ` Ingo Molnar
2008-05-05 21:36 ` Parag Warudkar
2008-05-05 21:49 ` Ingo Molnar
2008-05-06 0:38 ` Ingo Molnar
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=ce0170d90805051136w2f016c15p575623d33c220ddf@mail.gmail.com \
--to=sergio@uece.br \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parag.warudkar@gmail.com \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=torvalds@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 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®