From: Chen Zhongjin <chenzhongjin@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<x86@kernel.org>
Cc: <jpoimboe@redhat.com>, <peterz@infradead.org>,
<madvenka@linux.microsoft.com>, <tglx@linutronix.de>,
<mingo@redhat.com>, <bp@alien8.de>, <hpa@zytor.com>,
<arnd@arndb.de>, <akpm@linux-foundation.org>,
<andreyknvl@gmail.com>, <wangkefeng.wang@huawei.com>,
<andrealmeid@collabora.com>, <mhiramat@kernel.org>,
<mcgrof@kernel.org>, <christophe.leroy@csgroup.eu>,
<dmitry.torokhov@gmail.com>, <yangtiezhu@loongson.cn>,
<dave.hansen@linux.intel.com>
Subject: [PATCH 0/4] objtool: Reorganize x86 arch-specific code
Date: Tue, 31 May 2022 10:07:40 +0800 [thread overview]
Message-ID: <20220531020744.236970-1-chenzhongjin@huawei.com> (raw)
This patch set reorganize current x86 related code in objtool, [1-3] move
arch-specific to arch files and extract some common codes and [4] fixes
a cross-compile problem.
It make objtool more arch-generic, which makes other patches on different
architectures easier to be reviewed and merged.
Tested on x86 with unwind on kernel and module context.
Rebased to:
tip/objtool/core:22682a07acc3 (objtool: Fix objtool regression on x32 systems)
Chen Zhongjin (2):
objtool: Add generic symbol for relocation type
objtool: Specify host-arch for making LIBSUBCMD
Madhavan T. Venkataraman (2):
objtool: Make ORC type code arch-specific
objtool: Make ORC init and lookup code arch-generic
arch/x86/include/asm/unwind.h | 5 -
arch/x86/kernel/module.c | 7 +-
arch/x86/kernel/unwind_orc.c | 256 +----------------
arch/x86/kernel/vmlinux.lds.S | 2 +-
.../asm => include/asm-generic}/orc_lookup.h | 42 +++
kernel/Makefile | 2 +
kernel/orc_lookup.c | 261 ++++++++++++++++++
tools/objtool/Makefile | 2 +-
tools/objtool/arch/x86/Build | 1 +
tools/objtool/arch/x86/include/arch/elf.h | 5 +-
tools/objtool/arch/x86/orc.c | 137 +++++++++
tools/objtool/arch/x86/special.c | 5 +-
tools/objtool/check.c | 12 +-
tools/objtool/include/objtool/orc.h | 17 ++
tools/objtool/orc_dump.c | 59 +---
tools/objtool/orc_gen.c | 79 +-----
16 files changed, 491 insertions(+), 401 deletions(-)
rename {arch/x86/include/asm => include/asm-generic}/orc_lookup.h (51%)
create mode 100644 kernel/orc_lookup.c
create mode 100644 tools/objtool/arch/x86/orc.c
create mode 100644 tools/objtool/include/objtool/orc.h
--
2.17.1
next reply other threads:[~2022-05-31 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 2:07 Chen Zhongjin [this message]
2022-05-31 2:07 ` [PATCH 1/4] objtool: Make ORC type code arch-specific Chen Zhongjin
2022-05-31 2:07 ` [PATCH 2/4] objtool: Make ORC init and lookup code arch-generic Chen Zhongjin
2022-05-31 2:07 ` [PATCH 3/4] objtool: Add generic symbol for relocation type Chen Zhongjin
2022-05-31 2:07 ` [PATCH 4/4] objtool: Specify host-arch for making LIBSUBCMD Chen Zhongjin
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=20220531020744.236970-1-chenzhongjin@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@collabora.com \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=x86@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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).