From: Peter Zijlstra <peterz@infradead.org>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: Ruud van der Pas <ruud.vanderpas@oracle.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Bill Wendling <morbo@google.com>,
Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
clang-built-linux <llvm@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>, Yonghong Song <yhs@fb.com>,
Wenlei He <wenlei@fb.com>, Hongtao Yu <hoy@fb.com>,
Ingo Molnar <mingo@kernel.org>,
linux-toolchains@vger.kernel.org, elena.zannoni@oracle.com
Subject: Re: plumbers session on profiling?
Date: Fri, 1 Jul 2022 11:01:37 +0200 [thread overview]
Message-ID: <Yr638aOIaaEBPICy@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <878rpgpvfj.fsf@gnu.org>
On Tue, Jun 28, 2022 at 07:08:48PM +0200, Jose E. Marchesi wrote:
>
> [Added linux-toolchains@vger in CC]
>
> It would be interesting to have some discussion in the Toolchains track
> on building the kernel with PGO/FDO. I have seen a raise on interest on
> the topic in several companies, but it would make very little sense if
> no kernel hacker is interested in participating... anybody?
I know there's been a lot of work in this area, but none of it seems to
have trickled down to be easy enough for me to use it.
next prev parent reply other threads:[~2022-07-01 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 17:54 plumbers session on profiling? Nick Desaulniers
2022-04-15 20:41 ` Nick Desaulniers
2022-05-24 10:24 ` Jose E. Marchesi
2022-05-24 11:46 ` Ruud van der Pas
2022-06-21 22:02 ` Nick Desaulniers
2022-06-23 21:21 ` Ruud van der Pas
2022-06-28 17:08 ` Jose E. Marchesi
2022-06-29 19:48 ` Bill Wendling
2022-07-01 9:01 ` Peter Zijlstra [this message]
2022-07-01 10:17 ` Bill Wendling
2022-07-01 11:49 ` Peter Zijlstra
2022-07-01 13:50 ` Paul E. McKenney
[not found] ` <MW3PR15MB3868B1DC443B538A2A27F1D3CFBD9@MW3PR15MB3868.namprd15.prod.outlook.com>
2022-07-01 16:28 ` Paul E. McKenney
2022-07-01 18:57 ` Bill Wendling
2022-07-01 19:34 ` Fangrui Song
2022-07-04 14:03 ` Peter Zijlstra
2022-07-04 14:01 ` Peter Zijlstra
2022-07-05 12:57 ` Peter Zijlstra
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=Yr638aOIaaEBPICy@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=elena.zannoni@oracle.com \
--cc=hoy@fb.com \
--cc=jemarch@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=ruud.vanderpas@oracle.com \
--cc=samitolvanen@google.com \
--cc=vladimir.mezentsev@oracle.com \
--cc=wenlei@fb.com \
--cc=yhs@fb.com \
/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