Hello. To me, it looks rather a random failure. Is it actually reproducible
and proven that the patch has caused it? The patch doesn't seem to cause
the fails below.
Cheers,
Michael
On Wed, 30 Sep 2020, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-
27;ll send full patch after we're done testing this
>
> jirka
I've tested the change and seems OK to me.
Tested-by: Michael Petlan
>
> >
> > Thanks
> > Namhyung
> >
> >
> > >
> > > jirka
> > >
> > >
> &
On Fri, 26 Jun 2020, Andi Kleen wrote:
> > The name could be a metric or an event, the logic for each is quite
>
> I would say collisions are unlikely. Event names follow quite structured
> patterns.
But across various architectures? I guess event names can be arbitrary.
In perftool-testsuite, I
On Mon, 25 May 2020, Jiri Olsa wrote:
> hi,
> changes for using metric result in another metric seem
> to change lot of core metric code, so it's better we
> have some more tests before we do that.
>
> Sending as RFC as it's still alive and you guys might
> have some other idea of how to do this.
On Tue, 21 May 2019, Arnaldo Carvalho de Melo wrote:
> Em Tue, May 21, 2019 at 06:02:03AM +0300, Vitaly Chikunov escreveu:
> > When a host system has kernel headers that are newer than a compiling
> > kernel, mksyscalltbl fails with errors such as:
> >
> > : In function 'main':
> > :271:44: er
Commit-ID: 95f04328e42dc7d1eb08f3cb38150c1f2ec09f57
Gitweb: https://git.kernel.org/tip/95f04328e42dc7d1eb08f3cb38150c1f2ec09f57
Author: Michael Petlan
AuthorDate: Mon, 30 Jul 2018 17:35:04 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 31 Jul 2018 11:35:44 -0300
perf list
On Thu, 21 Jun 2018, Arnaldo Carvalho de Melo wrote:
Em Thu, Jun 21, 2018 at 11:19:15AM -0300, Arnaldo Carvalho de Melo escreveu:
Em Wed, Jun 20, 2018 at 07:45:46PM -0500, Kim Phillips escreveu:
On Wed, 20 Jun 2018 10:46:22 -0300
Arnaldo Carvalho de Melo wrote:
[...]
Would be good if we had
Commit-ID: 69b5c953400897a978f8a7d212c53aa90ff5027d
Gitweb: https://git.kernel.org/tip/69b5c953400897a978f8a7d212c53aa90ff5027d
Author: Michael Petlan
AuthorDate: Tue, 12 Dec 2017 11:22:03 -0500
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 27 Dec 2017 12:15:56 -0300
perf test
On Tue, 12 Dec 2017, Arnaldo Carvalho de Melo wrote:
[...]
> the point here is not to add any new patch for perf trace, etc, but find
> a way to fix just this test, so I think this works:
>
> # evts=$(echo $(perf list syscalls:sys_enter_open* |& egrep 'open(at)? ' |
> sed -r 's/.*sys_enter_([a-z]
Hey Arnaldo, this one did not remove the s390x hack and also, won't work
on arm. Please use the one I just have sent, few seconds ago...
On Tue, 12 Dec 2017, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 12, 2017 at 11:57:07AM -0300, Arnaldo Carvalho de Melo escreveu:
> > So the patch below does t
file you're using is the one in this
> patch submission?
So attaching all three patches to be sure. I have tested them on
two environments:
* x86_64 with 4.15.0-rc1
* aarch64 with 4.14.0
Both work with all three patches applied, applying on perf/core's
head (commit 26ea2ece7802f8fdaaacf321
On Tue, 15 Aug 2017, Arnaldo Carvalho de Melo wrote:
[...]
> > > Perhaps its time, yes. Some questions:
>
> > > Do these tests assume that perf was built in some particular way, i.e.
> > > as it is packaged for RHEL?
> >
> > Of course I run the testsuite most often on RHEL, but it should be
> > d
On Mon, 14 Aug 2017, Arnaldo Carvalho de Melo wrote:
> Em Mon, Aug 14, 2017 at 08:44:14PM +0200, Michael Petlan escreveu:
> > Hi Arnaldo!
> >
> > Maybe this would be the right time to incorporate the shell-based
> > perftool-testsuite [1] into perf-test, wouldn'
erf test shell: Install shell tests
>
> Now that we have shell tests, install them.
>
> Developers don't need this pass, as 'perf test' will look first at the
> in tree scripts at tools/perf/tests/shell/.
>
> Cc: Adrian Hunter
> Cc: David Ahern
> Cc: Ji
On Wed, 2015-09-23 at 11:08 +0100, Matt Fleming wrote:
[SNIP]
> > The RedHat QE has some more perf tool tests. There was some movement
> > to make those public, but not sure how it ended up.. ccing Michael Petlan
> > for news on this ;-)
>
> Cool! I'd definitely
15 matches
Mail list logo
