From: Andi Kleen <andi@firstfloor.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Richard Weinberger <richard@nod.at>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] x86: Disable CONFIG_X86_DECODER_SELFTEST in allmod/allyesconfigs
Date: Wed, 5 Feb 2014 18:32:02 +0100 [thread overview]
Message-ID: <20140205173202.GL11821@two.firstfloor.org> (raw)
In-Reply-To: <CAP=VYLrqOMw2ZYoeWnNK6r80_FmmCmdne1yA=VTaU1Q8phzaVg@mail.gmail.com>
> For the record, even with a (currently) modern CPU such as a
> Xeon E5-2630 @ 2.30GHz, the script takes 4m30s on 3.14-rc1
> i386 allyesconfig. And since it runs single threaded at the end
> of the build, it really adds that amount to the wall time spent
> on the build. So enthusiastically Acked, FWIW.
I suppose we could just multi thread it. It should
"embarassingly" scale without problems. But turning it off by default is a
first step.
-Andi
next prev parent reply other threads:[~2014-02-05 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 18:29 [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature Borislav Petkov
2014-02-03 22:00 ` David Rientjes
2014-02-03 22:47 ` Linus Torvalds
2014-02-03 22:57 ` Andrew Morton
2014-02-03 23:34 ` David Rientjes
2014-02-04 9:08 ` Ingo Molnar
2014-02-04 16:36 ` Linus Torvalds
2014-02-04 17:32 ` Andi Kleen
2014-02-04 18:41 ` Linus Torvalds
2014-02-05 5:51 ` [PATCH] x86: Disable CONFIG_X86_DECODER_SELFTEST in allmod/allyesconfigs Ingo Molnar
2014-02-05 16:17 ` Paul Gortmaker
2014-02-05 17:32 ` Andi Kleen [this message]
2014-02-10 13:31 ` [tip:x86/urgent] x86/debug: " tip-bot for Ingo Molnar
2014-02-11 0:01 ` [PATCH] x86: " Stephen Rothwell
2014-02-11 7:14 ` Ingo Molnar
2014-02-05 5:46 ` [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature Ingo Molnar
2014-02-04 4:59 ` Borislav Petkov
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=20140205173202.GL11821@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).