From: Andi Kleen <ak@linux.intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Omar Sandoval <osandov@fb.com>, linux-block@vger.kernel.org
Subject: Re: [REGRESSION] commit c2b3c170db610 causes blktests block/002 failure
Date: Fri, 16 Aug 2019 10:24:09 -0700 [thread overview]
Message-ID: <20190816172409.GA3216@tassilo.jf.intel.com> (raw)
In-Reply-To: <20190609181423.GA24173@mit.edu>
> The git bisect log (see attached) pointed at this commit:
bisect must be wrong. The commit only changes the perf tool, so cannot
break anything in the kernel.
-Andi
>
> commit c2b3c170db610896e4e633cba2135045333811c2 (HEAD, refs/bisect/bad)
> Author: Andi Kleen <ak@linux.intel.com>
> Date: Tue Mar 26 15:18:20 2019 -0700
>
> perf stat: Revert checks for duration_time
>
> This reverts e864c5ca145e ("perf stat: Hide internal duration_time
> counter") but doing it manually since the code has now moved to a
> different file.
>
> The next patch will properly implement duration_time as a full event, so
> no need to hide it anymore.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
> Link: http://lkml.kernel.org/r/20190326221823.11518-2-andi@firstfloor.org
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Is this a known issue?
prev parent reply other threads:[~2019-08-16 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 18:14 [REGRESSION] commit c2b3c170db610 causes blktests block/002 failure Theodore Ts'o
2019-06-18 23:09 ` Bart Van Assche
2019-06-27 17:14 ` Omar Sandoval
2019-06-28 16:20 ` Bart Van Assche
2019-06-27 20:24 ` Andi Kleen
2019-08-16 17:24 ` Andi Kleen [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=20190816172409.GA3216@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=tytso@mit.edu \
/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