From: Adrian Bunk <bunk@fs.tum.de>
To: John Cherry <cherry@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.1-mm5 (compile stats)
Date: Tue, 20 Jan 2004 23:27:00 +0100 [thread overview]
Message-ID: <20040120222700.GJ12027@fs.tum.de> (raw)
In-Reply-To: <1074636910.16765.14.camel@cherrytest.pdx.osdl.net>
On Tue, Jan 20, 2004 at 02:15:10PM -0800, John Cherry wrote:
>...
> > Regarding allnoconfig:
> > allnoconfig is a completely pathological case. It says "n" to support
> > for ISA, MCA and PCI, and neither networking nor any block devices.
> > Besides, it says "n" to ELF, a.out and other binary formats.
> > Demanding that allnoconfig should compile (although the resulting kernel
> > is completely useless) sounds a bit like demanding that no change in the
> > kernel is allowed to cause regressions in the dbench results...
> > It is useful to omit a common option like e.g. PCI and check whether the
> > kernel still compiles, but allnoconfig removes nearly everything and
> > compiles such a small part of the kernel, that it's hardly useful.
>
> I realize that allnoconfig is pathological, but it has caught several
> config errors. One would never try to boot from such a config. Builds
> based on allnoconfig have one purpose and that purpose is to validate
> that defines are not used in cases where they are NOT defined in the
> configuration. Developers will quite often code a feature or
> architecture with the config parameters always ON. When the config
> option is turned OFF, I will find compile errors, undefined variables,
> and the like. This is actually quite a valuable screen.
The problem is that allnoconfig turns _everything_ off.
Cases like e.g. CONFIG_PROC_FS=n are interesting, but allnoconfig
doesn't really test them since allnoconfig also says "n" to all drivers.
> If developers feel that this has outlived its usefulness, I'll remove it
> from the compile regressions. However, all I have received at this
> point have been requests to put an allnoconfig build into the
> regressions.
I'd like to hear from the people requesting it why they consider it
useful.
In my personal experience, compiling allyesconfig but with CONFIG_SMP=n
(which enables BROKEN_ON_SMP drivers), and compiling with gcc 2.95 are
more interesing (and more realistic) configurations than allnoconfig
that find many compile errors.
> John
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-20 22:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:05 2.6.1-mm5 Andrew Morton
2004-01-20 10:51 ` 2.6.1-mm5 dies booting, possibly network related Helge Hafting
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 13:45 ` [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Sean Neakums
2004-01-20 13:54 ` Vojtech Pavlik
2004-01-20 14:09 ` Sean Neakums
2004-01-20 16:08 ` 2.6.1-mm5 (compile stats) John Cherry
2004-01-20 21:57 ` Adrian Bunk
2004-01-20 22:15 ` John Cherry
2004-01-20 22:27 ` Adrian Bunk [this message]
2004-01-20 22:50 ` John Cherry
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:36 ` 2.6.1-mm5 Andrew Morton
2004-01-21 0:10 ` I2C sensors error (Re: 2.6.1-mm5) Zack Winkles
2004-01-21 0:34 ` Greg KH
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=20040120222700.GJ12027@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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