[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXcM/a8TUJYPcaGI@hirez.programming.kicks-ass.net>
Date: Mon, 25 Oct 2021 22:01:01 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Rob Landley <rob@...dley.net>,
Masahiro Yamada <masahiroy@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrii Nakryiko <andrii@...nel.org>
Subject: Re: Commit 0d989ac2c90b broke my x86-64 build.
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?
Powered by blists - more mailing lists