mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julien Thierry <jthierry@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jpoimboe@redhat.com, peterz@infradead.org, mbenes@suse.cz,
	benh@kernel.crashing.org
Subject: Re: [PATCH v4 0/4] Remove dependency of check subcmd upon orc
Date: Tue, 25 Aug 2020 13:49:07 +0100	[thread overview]
Message-ID: <3ef3dd0e-8820-1734-d11e-58a5c9390dd6@redhat.com> (raw)
In-Reply-To: <20200825124700.29616-1-jthierry@redhat.com>

Hi,

Sorry for the duplicate send. An issue happened while sending this one. 
Please ignore this thread.

Thanks,

Julien

On 8/25/20 1:46 PM, Julien Thierry wrote:
> Hi,
> 
> Matt Helsley's change[1] provided a base framework to opt-in/out
> objtool subcommands at compile time. This makes it easier for
> architectures to port objtool, one subcommand at a time.
> 
> Orc generation relies on the check operation implementation. However,
> the way this is done causes the check implementation to depend on the
> implementation of orc generation functions to call if orc generation is
> requested. This means that in order to implement check subcmd, orc
> subcmd also need to be implemented.
> 
> These patches aim at removing that dependency, having orc subcmd
> being built on top of the check subcmd.
> 
> 
> Changes since v3 [2]:
> - Rebased on v5.9-rc1
> - Renamed objtool_setup_file() to objtool_open_read()
> - Fixed misplaced elf_write() when file->elf->changed is true
> - Avoid additional allocation for orc data and compile out orc
>    definition when not needed instead
> 
> [1] https://www.spinics.net/lists/kernel/msg3510844.html
> [2] https://lkml.org/lkml/2020/7/30/415
> 
> Cheers,
> 
> Julien
> 
> -->
> 
> Julien Thierry (4):
>    objtool: Move object file loading out of check
>    objtool: Move orc outside of check
>    objtool: orc: Skip setting orc_entry for non-text sections
>    objtool: check: Use orc definition only when needed
> 
>   tools/objtool/Makefile        |  4 +++
>   tools/objtool/arch.h          |  2 ++
>   tools/objtool/builtin-check.c | 15 ++++++++++-
>   tools/objtool/builtin-orc.c   | 27 +++++++++++++++++++-
>   tools/objtool/check.c         | 47 ++++++-----------------------------
>   tools/objtool/check.h         |  2 ++
>   tools/objtool/objtool.c       | 29 +++++++++++++++++++++
>   tools/objtool/objtool.h       |  4 ++-
>   tools/objtool/orc_gen.c       |  3 +++
>   tools/objtool/weak.c          |  4 +--
>   10 files changed, 92 insertions(+), 45 deletions(-)
> 
> --
> 2.21.3
> 

-- 
Julien Thierry


  parent reply	other threads:[~2020-08-25 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 12:46 Julien Thierry
2020-08-25 12:46 ` [PATCH v4 1/4] objtool: Move object file loading out of check Julien Thierry
2020-08-25 12:46 ` [PATCH v4 2/4] objtool: Move orc outside " Julien Thierry
2020-08-25 12:49 ` Julien Thierry [this message]
2020-08-25 12:47 [PATCH v4 0/4] Remove dependency of check subcmd upon orc Julien Thierry
2020-09-01 16:05 ` 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=3ef3dd0e-8820-1734-d11e-58a5c9390dd6@redhat.com \
    --to=jthierry@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®