From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
x86@kernel.org
Subject: Re: [tip: objtool/core] objtool: Parse options from OBJTOOL_ARGS
Date: Thu, 4 Mar 2021 15:12:26 +0100 [thread overview]
Message-ID: <YEDqytNoqAMj1M+T@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <161476113169.20312.14290136035364654285.tip-bot2@tip-bot2>
On Wed, Mar 03, 2021 at 08:45:31AM -0000, tip-bot2 for Peter Zijlstra wrote:
> The following commit has been merged into the objtool/core branch of tip:
>
> Commit-ID: b52eb21aeca75790869c26b91b1d7b80b3946430
> Gitweb: https://git.kernel.org/tip/b52eb21aeca75790869c26b91b1d7b80b3946430
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Fri, 26 Feb 2021 11:32:30 +01:00
> Committer: Peter Zijlstra <peterz@infradead.org>
> CommitterDate: Wed, 03 Mar 2021 09:38:32 +01:00
>
> objtool: Parse options from OBJTOOL_ARGS
>
> Teach objtool to parse options from the OBJTOOL_ARGS environment
> variable.
>
> This enables things like:
>
> $ OBJTOOL_ARGS="--backup" make O=defconfig-build/ kernel/ponies.o
>
> to obtain both defconfig-build/kernel/ponies.o{,.orig} and easily
> inspect what objtool actually did.
Latest objdiff.sh to go with this:
$ cat objdiff.sh
#!/bin/bash
name=$1
pre=${name}.orig
post=${name}
function to_text {
obj=$1
( objdump -wdr $obj;
readelf -W --relocs --symbols $obj |
awk '/^Relocation section/ { $6=0 } { print $0 }'
) > ${obj}.tmp
}
to_text $pre
to_text $post
diff -u ${pre}.tmp ${post}.tmp
rm ${pre}.tmp ${post}.tmp
next prev parent reply other threads:[~2021-03-04 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 10:57 [PATCH 0/3] objtool: OBJTOOL_ARGS and --backup Peter Zijlstra
2021-02-26 10:57 ` [PATCH 1/3] objtool: Add --backup Peter Zijlstra
2021-02-26 11:48 ` Borislav Petkov
2021-03-02 11:58 ` Peter Zijlstra
2021-03-03 8:45 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2021-03-06 11:48 ` tip-bot2 for Peter Zijlstra
2021-02-26 10:57 ` [PATCH 2/3] objtool: Collate parse_options() users Peter Zijlstra
2021-03-03 8:45 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2021-03-06 11:48 ` tip-bot2 for Peter Zijlstra
2021-02-26 10:57 ` [PATCH 3/3] objtool: Parse options from OBJTOOL_ARGS Peter Zijlstra
2021-03-03 8:45 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2021-03-04 14:12 ` Peter Zijlstra [this message]
2021-03-06 11:48 ` tip-bot2 for Peter Zijlstra
2021-02-26 12:27 ` [PATCH 0/3] objtool: OBJTOOL_ARGS and --backup Peter Zijlstra
2021-03-03 0:29 ` 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=YEDqytNoqAMj1M+T@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.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