From: Josh Poimboeuf <jpoimboe@redhat.com>
To: x86@kernel.org
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/8] x86/asm: Add unwind hint annotations to head code
Date: Thu, 31 Aug 2017 15:23:38 -0500 [thread overview]
Message-ID: <cover.1504210919.git.jpoimboe@redhat.com> (raw)
Add some annotations to allow objtool to understand the head code.
Also do a few cleanups while I'm there.
Josh Poimboeuf (8):
objtool: Don't report end of section error after an empty unwind hint
x86/head: Remove confusing comment
x86/head: Remove unused 'bad_address' code
x86/head: Fix head ELF function annotations
x86/boot: Annotate verify_cpu() as a callable function
x86/xen: Fix xen head ELF annotations
x86/xen: Add unwind hint annotations
x86/head: Add unwind hint annotations
arch/x86/kernel/Makefile | 1 -
arch/x86/kernel/head_64.S | 27 +++++++++++++++------------
arch/x86/kernel/verify_cpu.S | 3 ++-
arch/x86/xen/xen-head.S | 10 +++++++---
tools/objtool/check.c | 7 +++++--
5 files changed, 29 insertions(+), 19 deletions(-)
--
2.13.5
next reply other threads:[~2017-08-31 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 20:23 Josh Poimboeuf [this message]
2017-08-31 20:23 ` [PATCH 1/8] objtool: Don't report end of section error after an empty unwind hint Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 2/8] x86/head: Remove confusing comment Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 3/8] x86/head: Remove unused 'bad_address' code Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 4/8] x86/head: Fix head ELF function annotations Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 5/8] x86/boot: Annotate verify_cpu() as a callable function Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 6/8] x86/xen: Fix xen head ELF annotations Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 7/8] x86/xen: Add unwind hint annotations Josh Poimboeuf
2017-09-12 12:56 ` Jiri Slaby
2017-09-12 15:39 ` Josh Poimboeuf
2017-08-31 20:23 ` [PATCH 8/8] x86/head: " Josh Poimboeuf
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=cover.1504210919.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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
Powered by JetHome