[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170608170844.134e1158@gandalf.local.home>
Date: Thu, 8 Jun 2017 17:08:44 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuah Khan <shuahkh@....samsung.com>
Cc: Shuah Khan <shuah@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-kselftest@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest
On Thu, 8 Jun 2017 14:06:23 -0600
Shuah Khan <shuahkh@....samsung.com> wrote:
> >>>>> # of passed: 41
> >>>>> # of failed: 1
> >>>>> # of unresolved: 0
> >>>>> # of untested: 0
> >>>>> # of unsupported: 3
> >>>>> # of xfailed: 0
> >>>>> # of undefined(test bug): 0
> >
> > I booted v4.12-rc4 with your config (didn't even have to change
> > anything for my box), and checkout the v4.12-rc4 kernel on the test box
> > and ran ftracetest. Here's my result:
> >
> > # of passed: 40
> > # of failed: 0
> > # of unresolved: 0
> > # of untested: 0
> > # of unsupported: 6
> > # of xfailed: 0
> > # of undefined(test bug): 0
> >
> > The unsupported were:
> >
> > [29] event trigger - test histogram modifiers [UNSUPPORTED]
> > [30] event trigger - test histogram trigger [UNSUPPORTED]
> > [31] event trigger - test multiple histogram triggers [UNSUPPORTED]
> >
> > [44] (instance) event trigger - test histogram modifiers [UNSUPPORTED]
> > [45] (instance) event trigger - test histogram trigger [UNSUPPORTED]
> > [46] (instance) event trigger - test multiple histogram triggers [UNSUPPORTED]
> >
> > Now why is this different? What compiler are you using to build your
> > kernel?
> >
> gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
>
>
> I don't see any regressions. I use this system for stable release testing
> and haven't seen any issues. Does ftrace have a dependency on a specific
> gcc revision?
It behaves differently with different gcc, as some support mfentry,
while others only use mcount. gcc 6.3.0 should be using mfentry. I'm
testing with 6.2, a build I made myself.
Just to confirm, you are running the 4.12-rc4 ftracetests on a 4.12-rc4
kernel and getting this error? Or are you running a different version
of ftracetest or a different version of the kernel?
-- Steve
>
>
> Full details:
> gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 6.3.0-12ubuntu2'
> --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs
> --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
> --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu-
> --enable-shared --enable-linker-build-id --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --libdir=/usr/lib
> --enable-nls --with-sysroot=/ --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
> --disable-vtable-verify --enable-libmpx --enable-plugin
> --enable-default-pie --with-system-zlib --disable-browser-plugin
> --enable-java-awt=gtk --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre
> --enable-java-home
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64
> --with-arch-directory=amd64
> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
> --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
> --disable-werror --with-arch-32=i686 --with-abi=m64
> --with-multilib-list=m32,m64,mx32 --enable-multilib
> --with-tune=generic --enable-checking=release
> --build=x86_64-linux-gnu --host=x86_64-linux-gnu
> --target=x86_64-linux-gnu Thread model: posix gcc version 6.3.0
> 20170406 (Ubuntu 6.3.0-12ubuntu2)
>
> gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
>
> thanks,
> -- Shuah
Powered by blists - more mailing lists