From: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux390-list@tuxmaker.boeblingen.de.ibm.com
Subject: Re: [PATCH] perf: fix perf test case 14 result reporting
Date: Tue, 6 Jun 2017 07:02:57 +0200 [thread overview]
Message-ID: <d7afbf7d-9ac8-20d6-5a5a-f20df660379d@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170602141105.GP2899@kernel.org>
On 06/02/2017 04:11 PM, Arnaldo Carvalho de Melo wrote:
[....]
>>
>> If you have specific patches in Jiri's branch that you think are good to
>> go, just point me to them and I'll cherry-pick them.
>>
>> I'm looking now at the one you pointed out above (070b9644981e).
>
> Just looked, but the cset comment should state what is the problem and
> how it is solved, right now it has just a one line summary :-\
>
> - Arnaldo
>
Looks like a misunderstanding. When I clone Jiri's tree and checkout
branch perf/attr_test:
url = git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
oc2666213455 12 $ git branch
master
* perf/attr_test
perf/stat
oc2666213455 13 $ git show 070b9644981e
commit 070b9644981e2dd160a6aae2723d0ec2d8b4c0b5
Author: Jiri Olsa <jolsa@kernel.org>
Date: Fri Mar 3 15:59:45 2017 +0100
perf tests attr: Do not store failed events
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 0dd7749..0f2b619 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -138,7 +138,7 @@ void test_attr__open(struct perf_event_attr *attr, pid_t pid, int cpu,
{
int errno_saved = errno;
- if (store_event(attr, pid, cpu, fd, group_fd, flags))
+ if ((fd != -1) && store_event(attr, pid, cpu, fd, group_fd, flags))
die("test attr FAILED");
errno = errno_saved;
oc2666213455 14 $
I get this commit which is another fix for an issue I discovered last week
while working on test case 14.
--
Thomas Richter, Dept 3303, IBM LTC Boeblingen Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2017-06-06 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170601123441.24581-1-tmricht@linux.vnet.ibm.com>
[not found] ` <20170601132038.GG2899@kernel.org>
[not found] ` <20170601210451.GA5713@krava>
2017-06-02 9:58 ` [PATCH] perf: fix perf test case 14 result reporting Thomas-Mich Richter
2017-06-02 14:09 ` Arnaldo Carvalho de Melo
2017-06-02 14:11 ` Arnaldo Carvalho de Melo
2017-06-04 18:51 ` Jiri Olsa
2017-06-06 5:02 ` Thomas-Mich Richter [this message]
2017-06-04 18:51 ` Jiri Olsa
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=d7afbf7d-9ac8-20d6-5a5a-f20df660379d@linux.vnet.ibm.com \
--to=tmricht@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux390-list@tuxmaker.boeblingen.de.ibm.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).