From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Adrian Bunk <bunk@kernel.org>,
Florian Fainelli <florian.fainelli@telecomint.eu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Add rdc321x defconfig file
Date: Tue, 26 Feb 2008 21:30:53 +0100 [thread overview]
Message-ID: <20080226203053.GB14350@elte.hu> (raw)
In-Reply-To: <20080226201442.GB32685@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> > Subarchitectures on x86 are just a shortcut for the "0.1% of systems
> > that were lazy to be properly abstracted into the general PC code". We
> > are discouraging additional subarches and the one that got added
> > recently will go away soon. The rest is legacy.
>
> So you say we would waste our time doing build test of the legacy
> sub-archs. OK.
definitely if what you want to do is to use your compilation resources
to increase the quality of a patch as efficiently as possible. Testing
UP/SMP 32bit/64bit defconfig and allnoconfig catches most of the
immediate problems - allmodconfig will catch most of the rest. If you
want to catch _all_ bugs that are possible the .config space, then 20
randconfig builds give a higher than 99.9% confidence factor already, in
my experience.
Sometimes, very rarely, deep down the chain of some really quirky
Kconfig dependencies, there can be up to 1:512 chance build bugs hiding,
which statistically need a 1000 randconfig builds to trigger. I saw a
few in the past, but they are really rare. No amount of pre-cooked
defconfigs would cover them - they are usually in drivers, not in
subarch support.
what would be really useful is an automatic Kconfig tree analysis, with
the printing out of too deep dependencies perhaps? Which might result in
the breaking down of too deep dependencies - to increase the coverage of
randconfig testing. Sometimes the number of "depends on" conditions are
mind-blowing.
Ingo
next prev parent reply other threads:[~2008-02-26 20:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 9:58 Florian Fainelli
2008-02-25 10:14 ` Ingo Molnar
2008-02-25 10:24 ` Florian Fainelli
2008-02-25 10:51 ` Ingo Molnar
2008-02-25 11:03 ` Florian Fainelli
2008-02-25 11:17 ` Adrian Bunk
2008-02-25 11:27 ` Florian Fainelli
2008-02-25 11:45 ` Adrian Bunk
2008-02-25 11:54 ` Ingo Molnar
2008-02-25 11:08 ` Adrian Bunk
2008-02-25 11:17 ` Ingo Molnar
2008-02-25 11:32 ` Adrian Bunk
2008-02-25 11:50 ` Ingo Molnar
2008-02-25 12:25 ` Adrian Bunk
2008-02-25 12:57 ` Ingo Molnar
2008-02-25 13:12 ` Adrian Bunk
2008-02-25 13:45 ` Ingo Molnar
2008-02-25 14:09 ` Adrian Bunk
2008-02-25 19:02 ` Sam Ravnborg
2008-02-26 9:44 ` Ingo Molnar
2008-02-26 20:14 ` Sam Ravnborg
2008-02-26 20:30 ` Ingo Molnar [this message]
2008-02-27 6:49 ` Adrian Bunk
2008-02-27 18:31 ` 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=20080226203053.GB14350@elte.hu \
--to=mingo@elte.hu \
--cc=bunk@kernel.org \
--cc=florian.fainelli@telecomint.eu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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®