From: Nick Desaulniers <ndesaulniers@google.com>
To: Will Deacon <will@kernel.org>
Cc: "Jose E. Marchesi" <jemarch@gnu.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ardb@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-toolchains@vger.kernel.org
Subject: Re: Linux Plumbers Conf 2021
Date: Wed, 16 Jun 2021 16:01:15 -0700 [thread overview]
Message-ID: <CAKwvOdmMNbKyrnRH79p77NgecAZNLf007i5ZSUb_j7waOZG9mQ@mail.gmail.com> (raw)
In-Reply-To: <20210518121447.GB7914@willie-the-truck>
+ linux-toolchains
On Tue, May 18, 2021 at 5:14 AM Will Deacon <will@kernel.org> wrote:
>
> Hi Nick,
>
> [+cc relevant folks]
>
> (sorry this is so late)
>
> On Tue, May 04, 2021 at 10:38:09AM -0700, Nick Desaulniers wrote:
> > This year the Linux Plumbers Conference (https://linuxplumbersconf.org) will
> > be fully virtual, and will happen from September 20-24th 2021.
> >
> > As part of the event, we are organizing a `Toolchains and Kernel
> > Micro-conference' devoted to discuss specific topics involving kernel and
> > toolchain. It will cover both the GNU Toolchain and LLVM.
> >
> > As in previous years, the emphasis will be in discussing specific topics that
> > require collaboration/interaction between the kernel and the toolchain chaps.
> > Examples of topics are wrapping of syscalls, specific features in the
> > compiler/linker/etc that are used by the kernel, desired optimizations,
> > features to alleviate security concerns on the kernel side, and the like.
> >
> > In order to get the Micro-Conference accepted we need to provide a list of
> > both topics and prospective attendants, so that's why I am reaching out to you
> > asking for:
> >
> > 1) Topics your project may want to discuss with the kernel hackers, during the
> > event.
> >
> > 2) Whether you are willing to contribute and/or participate in the
> > micro-conference.
> >
> > Please let us know @ jemarch@gnu.org & ndesaulniers@google.com.
>
> 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.
>
> Will
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2021-06-16 23:01 UTC|newest]
Thread overview: 16+ 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 ` Linux Plumbers Conf 2021 Josh Poimboeuf
2021-05-18 13:21 ` 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 [this message]
2021-06-24 20:35 ` Nick Desaulniers
2021-06-24 20:37 ` Nick Desaulniers
2021-06-28 17:59 ` Will Deacon
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=CAKwvOdmMNbKyrnRH79p77NgecAZNLf007i5ZSUb_j7waOZG9mQ@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jemarch@gnu.org \
--cc=jpoimboe@redhat.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).