From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH v2] perf tool: Provide an option to print perf_event_open args and return value
Date: Tue, 12 Nov 2019 19:30:06 +0530 [thread overview]
Message-ID: <85a6a2a2-0aa0-ef71-d2e7-816013e5f80d@linux.ibm.com> (raw)
In-Reply-To: <20191112113748.GL9365@kernel.org>
On 11/12/19 5:07 PM, Arnaldo Carvalho de Melo wrote:
>> [root@quaco ~]# perf test -v python
>> 18: 'import perf' in python :
>> --- start ---
>> test child forked, pid 19237
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> ImportError: /tmp/build/perf/python/perf.so: undefined symbol: debug_peo_args
>> test child finished with -1
>> ---- end ----
>> 'import perf' in python: FAILED!
>> [root@quaco ~]#
>>
>> Please always test your changes using 'perf test', before and after, to
>> see if some regression is being added. I'm trying to fix this one.
>
> I added this to fix this issue,
Sorry about that. Missed to run it. Will take care next time onwards.
Thanks for the fix.
-Ravi
next prev parent reply other threads:[~2019-11-12 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 3:59 [RFC] perf record: Add option to print perf_event_open args and return value Ravi Bangoria
2019-11-08 8:04 ` Jiri Olsa
2019-11-08 8:35 ` Ravi Bangoria
2019-11-08 9:30 ` [PATCH] perf tool: Provide an " Ravi Bangoria
2019-11-08 9:41 ` [PATCH v2] " Ravi Bangoria
2019-11-08 11:00 ` Jiri Olsa
2019-11-11 13:52 ` Arnaldo Carvalho de Melo
2019-11-12 11:29 ` Arnaldo Carvalho de Melo
2019-11-12 11:37 ` Arnaldo Carvalho de Melo
2019-11-12 14:00 ` Ravi Bangoria [this message]
2019-11-15 7:40 ` [tip: perf/core] " tip-bot2 for Ravi Bangoria
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=85a6a2a2-0aa0-ef71-d2e7-816013e5f80d@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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).