From: Josh Poimboeuf <jpoimboe@redhat.com>
To: changhuaixin <changhuaixin@linux.alibaba.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
bp@alien8.de, hpa@zytor.com, luto@amacapital.net,
michal.lkml@markovi.net, mingo@redhat.com, tglx@linutronix.de,
x86@kernel.org, yamada.masahiro@socionext.com
Subject: Re: [PATCH 0/2] Build ORC fast lookup table in scripts/sorttable tool
Date: Wed, 29 Apr 2020 23:06:54 -0500 [thread overview]
Message-ID: <20200430040654.mnkcfmj32tr6m3mg@treble> (raw)
In-Reply-To: <1CACF61E-FA7C-4986-AAD2-20A3B2BAC425@linux.alibaba.com>
On Thu, Apr 30, 2020 at 10:32:17AM +0800, changhuaixin wrote:
>
>
> > On Apr 29, 2020, at 4:49 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Wed, Apr 29, 2020 at 02:46:24PM +0800, Huaixin Chang wrote:
> >> Move building of fast lookup table from boot to sorttable tool. This saves us
> >> 6380us boot time on Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz with cores.
> >
> > And what does it add to the build time?
>
> It takes a little more than 7ms to build fast lookup table in
> sorttable on the same CPU. And it is on the critical path.
Thanks, I like it. It will help make the in-kernel unwinder even
simpler. And it will enable unwinding from early boot.
Maybe someday we can move all the table sorting code into objtool, once
we have objtool running on vmlinux.o.
I'll try to review the patches soon.
--
Josh
next prev parent reply other threads:[~2020-04-30 4:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 6:46 [PATCH 0/2] Build ORC fast lookup table in scripts/sorttable tool Huaixin Chang
2020-04-29 6:46 ` [PATCH 1/2] scripts/sorttable: Build orc fast lookup table via sorttable tool Huaixin Chang
2020-04-29 6:46 ` [PATCH 2/2] x86/unwind/orc: Remove unwind_init() from x86 boot Huaixin Chang
2020-04-29 8:49 ` [PATCH 0/2] Build ORC fast lookup table in scripts/sorttable tool Peter Zijlstra
2020-04-30 2:32 ` changhuaixin
2020-04-30 4:06 ` Josh Poimboeuf [this message]
2020-04-30 4:10 ` Josh Poimboeuf
2020-05-22 18:28 ` Josh Poimboeuf
2020-05-25 3:33 ` changhuaixin
[not found] ` <482837A8-E9D9-4229-B7B1-8E14403FB2AC@linux.alibaba.com>
2020-06-01 17:38 ` Josh Poimboeuf
2020-06-03 13:47 ` changhuaixin
2020-06-03 14:31 ` [PATCH v2 0/3] " Huaixin Chang
2020-06-03 14:31 ` [PATCH 1/3] scripts/sorttable: Change section type of orc_lookup to SHT_PROGBITS Huaixin Chang
2020-06-03 14:31 ` [PATCH 2/3] scripts/sorttable: Build orc fast lookup table via sorttable tool Huaixin Chang
2020-06-03 14:31 ` [PATCH 3/3] x86/unwind/orc: Simplify unwind_init() for x86 boot Huaixin Chang
2020-06-03 14:39 ` [PATCH v3 0/3] Build ORC fast lookup table in scripts/sorttable tool Huaixin Chang
2020-06-03 14:39 ` [PATCH 1/3] scripts/sorttable: Change section type of orc_lookup to SHT_PROGBITS Huaixin Chang
2020-06-03 14:39 ` [PATCH 2/3] scripts/sorttable: Build orc fast lookup table via sorttable tool Huaixin Chang
2020-06-03 14:39 ` [PATCH 3/3] x86/unwind/orc: Simplify unwind_init() for x86 boot Huaixin Chang
2020-06-29 2:14 ` [PATCH v3 0/3] Build ORC fast lookup table in scripts/sorttable tool changhuaixin
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=20200430040654.mnkcfmj32tr6m3mg@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=changhuaixin@linux.alibaba.com \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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