All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: mmarek@suse.cz, sam@ravnborg.org
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Rewriting kernel config after generation
Date: Fri, 2 Dec 2011 08:33:42 +0300	[thread overview]
Message-ID: <20111202053342.GA13877@p183.telecom.by> (raw)

I'm trying to add compiling with -march=native to the kernel.
The problem is that then some config options become discoverable at
the beginning of the compilation. For example,
CONFIG_X86_L1_CACHE_SHIFT=6 can be derived from "--param l1-cache-line-size=64".
I suspect this is no-go, because all the dependency logic must be
duplicated somewhere else (in the march=native script) for the above
to work.

Is there any cleaner way I'm missing?

In theory, such script could even turn off CONFIG_CPU_SUP_AMD
if it detects Intel CPU.

	Alexey

             reply	other threads:[~2011-12-02  5:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  5:33 Alexey Dobriyan [this message]
2011-12-06 11:45 ` Rewriting kernel config after generation Alexey Dobriyan
2011-12-10 14:27   ` Michal Marek

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=20111202053342.GA13877@p183.telecom.by \
    --to=adobriyan@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.