From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
patches@kernelci.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>,
lkft-triage@lists.linaro.org,
linux- stable <stable@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
jolsa@redhat.com, Namhyung Kim <namhyung@kernel.org>,
Leo Yan <leo.yan@linaro.org>, Basil Eljuse <Basil.Eljuse@arm.com>
Subject: Re: [PATCH 5.7 000/243] 5.7.10-rc2 review
Date: Thu, 23 Jul 2020 20:39:12 +0530 [thread overview]
Message-ID: <CA+G9fYsNCqKOAt1EdzvgDibpGnWVZum2RPJZe5CU8Ao-eYGyYA@mail.gmail.com> (raw)
In-Reply-To: <20200722124953.GE3155653@kroah.com>
On Wed, 22 Jul 2020 at 18:19, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> >
> > Results from Linaro’s test farm.
> > Regressions detected on arm and arm64 (Juno-r2)
> > We are bisecting this problem and get back to you soon.
> >
> > perf test cases failed
> > perf:
> > * Track-with-sched_switch
> > * perf_record_test
> > * perf_report_test
> >
> > Bad case:
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.002 MB perf-lava-test.data ]
> >
> > when it was pass it prints number of samples like below,
> > Good case:
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.004 MB perf-lava-test.data (46 samples) ]
> >
> > steps to reproduce:
> > # perf record -e cycles -o perf-lava-test.data ls -a 2>&1 | tee perf-record.log
> >
> > Link to full test:
> > https://qa-reports.linaro.org/lkft/linux-stable-rc-5.7-oe/build/v5.7.9-244-g7d2e5723ce4a/testrun/2969482/suite/perf/test/perf_record_test/log
> >
> > test case:
> > https://github.com/Linaro/test-definitions/blob/master/automated/linux/perf/perf.sh
>
> Any hint by bisection as to what this problem is caused by?
Not yet found the bad commit.
We are working on it.
- Naresh
next prev parent reply other threads:[~2020-07-23 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:16 [PATCH 5.7 000/243] 5.7.10-rc2 review Greg Kroah-Hartman
2020-07-20 23:37 ` Shuah Khan
2020-07-21 10:42 ` Greg Kroah-Hartman
2020-07-21 9:29 ` Naresh Kamboju
2020-07-22 12:49 ` Greg Kroah-Hartman
2020-07-23 15:09 ` Naresh Kamboju [this message]
2020-07-21 13:17 ` Thierry Reding
2020-07-22 12:47 ` Greg Kroah-Hartman
2020-07-21 16:38 ` Guenter Roeck
2020-07-22 12:49 ` Greg Kroah-Hartman
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=CA+G9fYsNCqKOAt1EdzvgDibpGnWVZum2RPJZe5CU8Ao-eYGyYA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=Basil.Eljuse@arm.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=patches@kernelci.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).