From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Rob Landley <rob@landley.net>,
Masahiro Yamada <masahiroy@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: Commit 0d989ac2c90b broke my x86-64 build.
Date: Mon, 25 Oct 2021 22:01:01 +0200 [thread overview]
Message-ID: <YXcM/a8TUJYPcaGI@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211025185945.ywcvhqypzoaxohyc@treble>
On Mon, Oct 25, 2021 at 11:59:45AM -0700, Josh Poimboeuf wrote:
> Plus it's a good idea to make the dependencies more explicit. We've
> already been looking at modularizing, like creating a new CONFIG_OBJTOOL
> option and splitting stack validation out from some of the other
> features. This could be a nice extension of that.
>
> Which reminds me, I'm still thinking we need to make the interface more
> easily combinable, like:
>
> objtool run \
> [--validate] \
> [--noinstr] \
> [--retpoline] \
> [--orc] \
> [--mcount] \
> [--static-call] \
> [--kcov] \
> [--frame-pointer] \
> [--vmlinux] \
> [--uaccess] \
> [--module] \
> [--no-unreachable] \
> [--backup] \
> [--stats] \
> [--backtrace]
>
> objtool dump \
> [--orc] \
> [--mcount] \
> [--static-call] \
> [--alternatives] \
> [--whatever]
>
> I can hopefully get to it one of these weeks...
Yes, that would be nice.
Also, unrelated, were you going to do that .fixup cleanup for x86_64 or
should I try and squeeze it in?
next prev parent reply other threads:[~2021-10-25 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 6:36 Commit 0d989ac2c90b broke my x86-64 build Rob Landley
2021-10-24 18:13 ` Masahiro Yamada
2021-10-24 19:27 ` Josh Poimboeuf
2021-10-25 2:51 ` Rob Landley
2021-10-25 9:04 ` Peter Zijlstra
2021-10-25 14:46 ` Josh Poimboeuf
2021-10-25 14:56 ` Peter Zijlstra
2021-10-25 18:59 ` Josh Poimboeuf
2021-10-25 20:01 ` Peter Zijlstra [this message]
2021-10-26 3:33 ` 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=YXcM/a8TUJYPcaGI@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrii@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rob@landley.net \
/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