public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Pintu Kumar <pintu.ping@gmail.com>
Cc: "Wangnan \(F\)" <wangnan0@huawei.com>,
	Alexis Berlemont <alexis.berlemont@gmail.com>,
	daniel@iogearbox.net, kernelnewbies@kernelnewbies.org,
	alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org,
	acme@redhat.com, peterz@infradead.org, mingo@redhat.com,
	huawei.libin@huawei.com, naveen.n.rao@linux.vnet.ibm.com,
	quentin.monnet@netronome.com, maddy@linux.vnet.ibm.com,
	davem@davemloft.net
Subject: Re: [perf] perf test BPF fails on 4.9.20
Date: Mon, 5 Feb 2018 22:54:02 +0900	[thread overview]
Message-ID: <20180205225402.f0b2448650763bc5cb8099a8@kernel.org> (raw)
In-Reply-To: <CAOuPNLgnazHNKoMozZq7Ef=rEwRG=rwktsnp8jCKCD0gMH+hbg@mail.gmail.com>

On Mon, 5 Feb 2018 15:17:41 +0530
Pintu Kumar <pintu.ping@gmail.com> wrote:

> On Sat, Feb 3, 2018 at 6:49 PM, Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > Hi Pintu,
> >
> > On Fri, 2 Feb 2018 19:03:30 +0530
> > Pintu Kumar <pintu.ping@gmail.com> wrote:
> >
> >> Hi All,
> >>
> >> I have fixed both the issue with perf test.
> >>
> >> 1) 16: Try 'import perf' in python, checking link problems      : FAILED!
> >> To fix this issue, I have to install:
> >> pip install --upgrade pip
> >> pip2.7 install perf
> >>
> >> 2) 37.2: Test BPF prologue generation                           : FAILED!
> >> To fix this issue I had to enable full version of CONFIG_DEBUG_INFO in kernel.
> >>
> >> Now, my question is:
> >> Is it possible to pass BPF test without enabling CONFIG_DEBUG_INFO in kernel ?
> >
> > It depends on what BPF test does, but it seems to access local vars. This means
> > you need to enable CONFIG_DEBUG_INFO. With debuginfo we can find the assignment
> > of register/stack for each local variable.
> >
> 
> OK. Thank you so much for your reply.
> I think we don't need BPF test at this time.
> Is it possible to disable/skip it ?

It depends on what you want to do with perf. If you don't use BPF, yes, you can
skip it :)

Thank you,

-- 
Masami Hiramatsu <mhiramat@kernel.org>

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

  reply	other threads:[~2018-02-05 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02  7:55 [perf] perf test BPF fails on 4.9.20 Pintu Kumar
2018-02-02 13:33 ` Pintu Kumar
2018-02-03 13:19   ` Masami Hiramatsu
2018-02-05  9:47     ` Pintu Kumar
2018-02-05 13:54       ` Masami Hiramatsu [this message]
2018-02-05 17:06         ` 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=20180205225402.f0b2448650763bc5cb8099a8@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexis.berlemont@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=huawei.libin@huawei.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mingo@redhat.com \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pintu.ping@gmail.com \
    --cc=quentin.monnet@netronome.com \
    --cc=wangnan0@huawei.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