From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Kan Liang <kan.liang@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
Ian Rogers <irogers@google.com>, Song Liu <songliubraving@fb.com>,
"Jin, Yao" <yao.jin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Jonatan Corbet <corbet@lwn.net>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: BoF on LPC 2019 : Linux Perf advancements for compute intensive and server systems
Date: Tue, 27 Aug 2019 09:48:02 +0200 [thread overview]
Message-ID: <20190827074802.GA22896@krava> (raw)
In-Reply-To: <20190826221021.GB21761@kernel.org>
On Mon, Aug 26, 2019 at 07:10:21PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Aug 26, 2019 at 10:57:58AM -0700, Andi Kleen escreveu:
> > >
> > > >
> > > > All those are already merged, after long reviewing phases and lots of
> > > > testing, right?
> > >
> > > Right. These changes now constitute parts of the Linux kernel source tree.
> >
> > Might be better to focus on future areas that haven't been merged yet.
>
> Agreed, we can have a initial, short report on what has been done to
> address these issues, and I think Alexey could take care of that, but
> then we should try and list here what else in addition to what Ian et
> all listed on their talk.
>
> And perhaps even things that ammeliorate the problems they list there,
> i.e. Ian, Stephane, the things that Alexey listed were already
> tested/considered by you guys?
there's also ongoing work on adding threads to perf record:
https://lore.kernel.org/lkml/20180913125450.21342-1-jolsa@kernel.org/#t
currently being stuck on me sending the perf_sesion changes
Alexey ran some initial benchmarks and it seems to perform nicely,
not sure we discussed the results on list thought
jirka
prev parent reply other threads:[~2019-08-27 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 11:36 BoF on LPC 2019 : Linux Perf advancements for compute intensive and server systems Alexey Budankov
2019-08-26 13:55 ` Arnaldo Carvalho de Melo
2019-08-26 14:25 ` Alexey Budankov
2019-08-26 17:57 ` Andi Kleen
2019-08-26 22:10 ` Arnaldo Carvalho de Melo
2019-08-27 7:48 ` Jiri Olsa [this message]
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=20190827074802.GA22896@krava \
--to=jolsa@redhat.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=corbet@lwn.net \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=yao.jin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).