From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
peterz@infradead.org, ardb@kernel.org, catalin.marinas@arm.com,
mark.rutland@arm.com, linux-toolchains@vger.kernel.org
Subject: Re: Linux Plumbers Conf 2021
Date: Tue, 18 May 2021 07:48:19 -0500 [thread overview]
Message-ID: <20210518124819.lkzzgjcrh4cc5a6i@treble> (raw)
In-Reply-To: <20210518124311.r4fwv6lfz3erkqnb@treble>
Fixing linux-toolchains list address.
On Tue, May 18, 2021 at 07:43:13AM -0500, Josh Poimboeuf wrote:
> On Tue, May 18, 2021 at 01:14:48PM +0100, Will Deacon wrote:
> > If it's not too late, I'd definitely be interested in a discussion around
> > objtool support for arm64. Specifically, I would very much like us _not_
> > to have a hard dependency on objtool and instead treat it as a binary
> > linter of sorts. However, this likely requires help from the toolchain
> > where some of the jobs which are performed by objtool on x86 today now
> > need to be done by the compiler/linker for arm64.
> >
> > I don't have a good handle on exactly what is needed and whether there's
> > any appetite from the toolchain developers to implement this, so it would
> > be very helpful to kick that discussion off.
>
> Objtool stack validation already is pretty much a "binary linter". If
> all the warnings are fixed then we can trust the unwind metadata (e.g.
> frame pointers) for reliable unwinding / live patching.
>
> All warnings are expected to be fixed by humans, so objtool doesn't have
> to edit the binary (assuming no ORC, which is optional). Objtool is
> only considered a hard dependency for live patching because unfixed
> warnings could mean a livepatch fail.
>
> So I wonder what specifically you have in mind?
>
> --
> Josh
--
Josh
next parent reply other threads:[~2021-05-18 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKwvOdm-Vb2BGRCmtYCh5JcGkM+XedzSMdNr8kQLbY4y_85EvA@mail.gmail.com>
[not found] ` <20210518121447.GB7914@willie-the-truck>
[not found] ` <20210518124311.r4fwv6lfz3erkqnb@treble>
2021-05-18 12:48 ` Josh Poimboeuf [this message]
2021-05-18 13:21 ` Linux Plumbers Conf 2021 Peter Zijlstra
2021-05-18 16:57 ` Nick Desaulniers
2021-05-18 20:03 ` Peter Zijlstra
2021-05-18 20:15 ` Nick Desaulniers
2021-05-19 9:32 ` Mark Rutland
2021-05-19 10:19 ` Marco Elver
2021-05-19 11:56 ` Mark Rutland
2021-05-19 14:04 ` Marco Elver
2021-05-19 15:02 ` Martin Liška
2021-05-19 15:05 ` Marco Elver
2021-05-20 8:34 ` Martin Liška
2021-06-16 23:01 ` Nick Desaulniers
2021-06-24 20:35 ` Nick Desaulniers
2021-06-24 20:37 ` Nick Desaulniers
2021-06-28 17:59 ` Will Deacon
2021-05-04 17:34 Nick Desaulniers
2021-06-24 20:31 ` Nick Desaulniers
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=20210518124819.lkzzgjcrh4cc5a6i@treble \
--to=jpoimboe@redhat.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jemarch@gnu.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.