From: David Daney <ddaney.cavm@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-embedded@vger.kernel.org, x86@kernel.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH RFC 1/5] scripts: Add sortextable to sort the kernel's exception table.
Date: Mon, 21 Nov 2011 10:25:36 -0800 [thread overview]
Message-ID: <4ECA97A0.3090005@gmail.com> (raw)
In-Reply-To: <201111201822.13614.vapier@gentoo.org>
On 11/20/2011 03:22 PM, Mike Frysinger wrote:
> On Friday 18 November 2011 14:37:44 David Daney wrote:
>> --- /dev/null
>> +++ b/scripts/sortextable.c
>>
>> +/*
>> + * sortextable.c: Sort the kernel's exception table
>> + *
>> + * Copyright 2011 Cavium, Inc.
>> + *
>> + * Based on code taken from recortmcount.c which is:
>
> seems like it'd be nice if the duplicate helper funcs were placed in a common
> header file rather than copying& pasting between them.
>
Yes, I may try to factor out some common code if we decide to move
forward with the patch set.
>> + switch (w2(ehdr->e_machine)) {
>> + default:
>> + fprintf(stderr, "unrecognized e_machine %d %s\n",
>> + w2(ehdr->e_machine), fname);
>> + fail_file();
>> + break;
>> + case EM_386:
>> + case EM_MIPS:
>> + case EM_X86_64:
>> + break;
>> + } /* end switch */
>
> unlike recordmcount, this file doesn't do anything arch specific. so let's just
> delete this and be done.
Not really true at this point. We don't know the size or layout of the
architecture specific exception table entries, likewise for
CONFIG_ARCH_HAS_SORT_EXTABLE, we don't even know how to do the comparison.
I was trying to be a little conservative and only apply the build time
sort to configurations that I could test.
David Daney
next prev parent reply other threads:[~2011-11-21 18:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 19:37 [PATCH RFC 0/5] Speed booting by sorting exception tables at build time David Daney
2011-11-18 19:37 ` David Daney
2011-11-18 19:37 ` [PATCH RFC 1/5] scripts: Add sortextable to sort the kernel's exception table David Daney
2011-11-18 19:37 ` David Daney
2011-11-20 23:22 ` Mike Frysinger
2011-11-20 23:22 ` Mike Frysinger
2011-11-21 18:25 ` David Daney [this message]
2011-11-21 18:50 ` Mike Frysinger
2011-11-21 19:16 ` David Daney
2011-11-21 20:08 ` Mike Frysinger
2011-11-21 20:08 ` Mike Frysinger
2011-11-20 23:26 ` H. Peter Anvin
2011-11-20 23:27 ` H. Peter Anvin
2011-11-20 23:28 ` David Woodhouse
2011-11-20 23:30 ` H. Peter Anvin
2011-11-21 18:51 ` David Daney
2011-11-21 18:51 ` David Daney
2011-11-18 19:37 ` [PATCH RFC 2/5] extable: Skip sorting if sorted at build time David Daney
2011-11-18 19:37 ` [PATCH RFC 3/5] kbuild/extable: Hook up sortextable into the build system David Daney
2011-11-20 13:45 ` Michal Marek
2011-11-22 21:38 ` David Daney
2011-11-18 19:37 ` [PATCH RFC 4/5] MIPS: Select BUILDTIME_EXTABLE_SORT David Daney
2011-11-18 19:37 ` David Daney
2011-11-18 19:37 ` [PATCH RFC 5/5] x86: " David Daney
2011-11-18 19:37 ` David Daney
2011-11-20 23:10 ` [PATCH RFC 0/5] Speed booting by sorting exception tables at build time Mike Frysinger
2011-11-20 23:10 ` Mike Frysinger
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=4ECA97A0.3090005@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=david.daney@cavium.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vapier@gentoo.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).