mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nico Schottelius <nico-linux-20090703@schottelius.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reliable rebuild different kernel versions with the same config?
Date: Fri, 3 Jul 2009 09:07:29 -0700	[thread overview]
Message-ID: <20090703090729.8c95a1e7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20090703144640.GA24922@ikn.schottelius.org>

On Fri, 3 Jul 2009 16:46:42 +0200 Nico Schottelius wrote:

> Hello!
> 
> We encounter very strange delays here in a test application
> on different kernels. To debug it a bit better, we would like to
> 
> - start the application, store results
> - build the next older kernel
> - install it
> - boot it
> - goto 1 (*)
> 
> The problem is, that after changing the version, make all or make oldconfig
> prompt us to fillout some values, which is problematic, because we
> want to run it automatically.

Use:
$ yes "" | make oldconfig
to supply replies to the prompts.

> Is there a way to use a base config, that includes support for the
> hardware (ibm x3550 m2) and all the other values are adopted from
> default values?

See Documentation/kbuild/kconfig.txt, the section on KCONFIG_ALLCONFIG.
I use this quite a bit.

> make defconfig && cat myconfig >> .config does not do the trick :-)

That needs a "make oldconfig" afterwards, then it might work.

> Sincerly,
> 
> Nico
> 
> (*): This is so far already automated, have a look at
>   http://git.schottelius.org/?p=nsbin;a=commit;h=31461434cbda96bfb71c741c9510b1d92dcbb161
> 
> -- 
> Currently moving *.schottelius.org to http://www.nico.schottelius.org/ ...


---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

  reply	other threads:[~2009-07-03 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 14:46 Nico Schottelius
2009-07-03 16:07 ` Randy Dunlap [this message]
2009-07-04 14:23   ` Nico Schottelius

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=20090703090729.8c95a1e7.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-linux-20090703@schottelius.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®