linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wangnan (F)" <wangnan0@huawei.com>
To: Pintu Kumar <pintu.ping@gmail.com>,
	<linux-kernel@vger.kernel.org>, <kernelnewbies@kernelnewbies.org>,
	<quentin.monnet@netronome.com>, <daniel@iogearbox.net>,
	<davem@davemloft.net>, <acme@redhat.com>,
	<alexander.shishkin@linux.intel.com>, <mingo@redhat.com>
Subject: Re: [tools/perf] perf test LLVM failure on 4.9
Date: Wed, 24 Jan 2018 09:09:51 +0800	[thread overview]
Message-ID: <6e70d220-6f79-38d6-68bb-a21a9bd89bc1@huawei.com> (raw)
In-Reply-To: <CAOuPNLj-8=xsNxUrRA6ZUCW5qkjnUWFTA0vpA=0H2O1PcVrtcA@mail.gmail.com>



On 2018/1/23 20:37, Pintu Kumar wrote:
> Hi All,
>
> I am verifying all perf tests on Ubuntu-16 x86-64 platform using the
> kernel version 4.9.20.
> I have installed several others packages including: clang, llvm
>
> But, when I run 'perf test' I get some FAILURE.
> Specially, 'perf test LLVM' is failing.
>
> Please check the below error logs:
>
> ----------------------------------------------------
> # perf test LLVM
> 35: Test LLVM searching and compiling                        :
> 35.1: Basic BPF llvm compiling test                          : FAILED!
> 35.2: Test kbuild searching                                  : Skip
> 35.3: Compile source for BPF prologue generation test        : Skip
> 35.4: Compile source for BPF relocation test                 : Skip
> ----------------------------------------------------
>
> When I run with -v I get this:
>
> -----------------------------------------------------
> # perf test -v LLVM
> 35: Test LLVM searching and compiling                        :
> 35.1: Basic BPF llvm compiling test                          :
> --- start ---
> test child forked, pid 3304
> Unablt to get kernel version from uname '4.9-xxxx-amd-x86-64'
> WARNING:        unable to get correct kernel building directory.
> Hint:   Set correct kbuild directory using 'kbuild-dir' option in [llvm]
>          section of ~/.perfconfig or set it to "" to suppress kbuild
>          detection.
>
> Unablt to get kernel version from uname '4.9-xxxx-amd-x86-64'
>
>
> int _version SEC("version") = LINUX_VERSION_CODE;
> ' | $CLANG_EXEC -D__KERNEL__ -D__NR_CPUS__=$NR_CPUS
> -DLINUX_VERSION_CODE=$LINUX_VERSION_CODE $CLANG_OPTIONS
> $KERNEL_INC_OPTIONS -Wno-unused-value -Wno-pointer-sign
> -working-directory $WORKING_DIR -c "$CLANG_SOURCE" -target bpf -O2 -o
> -
> libbpf: 2129190-4a0 doesn't provide kernel version
> Failed to parse test case 'Basic BPF llvm compiling test'
> test child finished with -1
> ---- end ----
> Test LLVM searching and compiling subtest 0: FAILED!
> -----------------------------------------------------
>
>
> Basic BPF LLVM compiling test is failing.
> It reports that bpf could not able to read the kernel version from uname.
> Is it because of this that 'perf test LLVM' is failing ?
>
> My uname says:
> 4.9-xxxx-amd-x86-64

'perf test LLVM' requires a well formed uname string (%d.%d.%d). Please see
tools/perf/fetch_kernel_version . If your distro uses another method to 
report
kernel version number (from your uname string, sublevel can't be 
determined),
please help us improve that function like what we have done for ubuntu
(checking /proc/version_signature).


> My kernel version is: 4.9.20 (from Makefile)
>
> So, I dont think there is any problem with kernel version.
>
> If any body have come across this problem please let me know how to
> resolve this issue.
>
>
>
> Thank You!
>
> Regards,
> Pintu



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2018-01-24  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 12:37 [tools/perf] perf test LLVM failure on 4.9 Pintu Kumar
2018-01-23 13:17 ` Arnaldo Carvalho de Melo
2018-01-23 18:55 ` valdis.kletnieks
2018-01-24  1:09 ` Wangnan (F) [this message]
2018-01-24 14:53   ` Pintu Kumar

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=6e70d220-6f79-38d6-68bb-a21a9bd89bc1@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pintu.ping@gmail.com \
    --cc=quentin.monnet@netronome.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;
as well as URLs for NNTP newsgroup(s).