linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Helsley <mhelsley@vmware.com>
To: <linux-kernel@vger.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Julien Thierry <jthierry@redhat.com>,
	Matt Helsley <mhelsley@vmware.com>
Subject: [PATCH 0/2] objtool: Support implicit addend relocations
Date: Fri, 29 May 2020 14:01:12 -0700	[thread overview]
Message-ID: <cover.1590785960.git.mhelsley@vmware.com> (raw)

Future tools that use objtool to process ELF object files may require
reading or even modifying relocations with implicit addends. This
series cleans up the naming of the relocation struct in objtool,
variable names, and function names to be consistent with a more
generic use rather than being specific to those applying explicit
addends.

Changes since RFC [1]:
* Dropped the second patch and rebased on tip objtool/core with
  patch[2] from Sami Tolvanen [Josh Poimboeuf]
* Remade the rename patch with a sed script and added script to
  the commit message to aid backports. [Josh]
* Removed function pointers from last patch. [Josh]
* Added relocation type parameter to elf_create_reloc_section()
  to match pattern with relocation section rebuilding.

[1] https://lore.kernel.org/lkml/cover.1590597288.git.mhelsley@vmware.com
[2] https://lore.kernel.org/lkml/20200421182501.149101-1-samitolvanen@google.com/


Matt Helsley (2):
  objtool: Rename rela to reloc
  objtool: Add support for relocations without addends

 tools/objtool/arch.h            |   2 +-
 tools/objtool/arch/x86/decode.c |   2 +-
 tools/objtool/check.c           | 190 +++++++++++------------
 tools/objtool/check.h           |   2 +-
 tools/objtool/elf.c             | 262 +++++++++++++++++++++++---------
 tools/objtool/elf.h             |  27 ++--
 tools/objtool/orc_gen.c         |  44 +++---
 tools/objtool/special.c         |  22 +--
 8 files changed, 333 insertions(+), 218 deletions(-)


base-commit: 0decf1f8de919782b152daf9c991967a2bac54f0
prerequisite-patch-id: 83ac956b6b4a769cafcdc4abaea4a3bcc3136d6d
-- 
2.20.1


             reply	other threads:[~2020-05-29 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 21:01 Matt Helsley [this message]
2020-05-29 21:01 ` [PATCH 1/2] objtool: Rename rela to reloc Matt Helsley
2020-05-29 23:22   ` Josh Poimboeuf
2020-05-30  0:52     ` Matt Helsley
2020-06-01 15:09       ` Josh Poimboeuf
2020-05-29 21:01 ` [PATCH 2/2] objtool: Add support for relocations without addends Matt Helsley
2020-06-02  7:36   ` Julien Thierry
2020-06-02 16:12   ` Kamalesh Babulal

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.1590785960.git.mhelsley@vmware.com \
    --to=mhelsley@vmware.com \
    --cc=jpoimboe@redhat.com \
    --cc=jthierry@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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).