From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
Joe Stringer <joe@ovn.org>, Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Wang Nan <wangnan0@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/4] perf/urgent fixes for 'perf sched timehist' and samples/bpf/ testing
Date: Fri, 23 Dec 2016 20:24:18 +0100 [thread overview]
Message-ID: <20161223192418.GA21937@gmail.com> (raw)
In-Reply-To: <20161223021252.11225-1-acme@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> P.S.: Some of the container test builds now include building samples/bpf/ with:
>
> $ make O=/tmp/build/linux allmodconfig
> $ make O=/tmp/build/linux headers_install
> $ make O=/tmp/build/linux samples/bpf/
>
> In distributions having at least clang/llvm 3.8+ with the 'bpf' target.
>
> Examples include debian:experimental, fedora:rawhide and opensuse:tumbleweed,
> more to come as I go over rebuilding the containers looking for more suitable
> environments.
>
> This will help in finding regressions in this area, now using tools/lib/bpf/.
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 1134c2b5cb840409ffd966d8c2a9468f64e6a494:
>
> perf/x86: Fix overlap counter scheduling bug (2016-12-22 17:45:43 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo-20161222
>
> for you to fetch changes up to bdd75729e5d279d734e8d3fb41ef4818ac1598ab:
>
> perf sched timehist: Fix invalid period calculation (2016-12-22 16:35:46 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> Fixes for 'perf sched timehist': (Namhyung Kim)
>
> - Define a larger initial alignment value for the COMM column and
> make it be more consistently honoured, for instance in the header.
>
> - Fix invalid period calculation when using the --time option to
> select a time slice, when events outside that slice were being
> considered for the per cpu idle stats summary.
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Namhyung Kim (4):
> perf sched timehist: Honour 'comm_width' when aligning the headers
> perf sched timehist: Enlarge default 'comm_width'
> perf sched timehist: Remove hardcoded 'comm_width' check at print_summary
> perf sched timehist: Fix invalid period calculation
>
> tools/perf/builtin-sched.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
prev parent reply other threads:[~2016-12-23 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 2:12 [GIT PULL 0/4] perf/urgent fixes for 'perf sched timehist' and samples/bpf/ testing Arnaldo Carvalho de Melo
2016-12-23 2:12 ` [PATCH 1/4] perf sched timehist: Honour 'comm_width' when aligning the headers Arnaldo Carvalho de Melo
2016-12-23 2:12 ` [PATCH 2/4] perf sched timehist: Enlarge default 'comm_width' Arnaldo Carvalho de Melo
2016-12-23 2:12 ` [PATCH 3/4] perf sched timehist: Remove hardcoded 'comm_width' check at print_summary Arnaldo Carvalho de Melo
2016-12-23 2:12 ` [PATCH 4/4] perf sched timehist: Fix invalid period calculation Arnaldo Carvalho de Melo
2016-12-23 14:54 ` [GIT PULL 0/4] perf/urgent fixes for 'perf sched timehist' and samples/bpf/ testing Namhyung Kim
2016-12-23 19:24 ` Ingo Molnar [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=20161223192418.GA21937@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=joe@ovn.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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