From: Jiri Olsa <jolsa@redhat.com>
To: Thomas Richter <tmricht@linux.vnet.ibm.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH 1/2] perf test attr: fix python error on empty result
Date: Fri, 15 Sep 2017 20:45:03 +0200 [thread overview]
Message-ID: <20170915184503.GA31734@krava> (raw)
In-Reply-To: <20170913081209.39570-1-tmricht@linux.vnet.ibm.com>
On Wed, Sep 13, 2017 at 10:12:08AM +0200, Thomas Richter wrote:
> Commit d78ada4a767 ("perf tests attr: Do not store failed events")
> does not create an event file in the /tmp directory when the
> perf_open_event() system call failed.
> This can lead to a situation where not /tmp/event-xx-yy-zz result
> file exists at all (for example on a s390x virtual machine environment)
> where no CPUMF hardware is available.
those 2 were already sent earlier if I'm not mistaken,
I think I've already acked them, if not:
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2017-09-15 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 8:12 [PATCH 1/2] perf test attr: fix python error on empty result Thomas Richter
2017-09-13 8:12 ` [PATCH 2/2] perf test attr: fix ignored test case result Thomas Richter
2017-09-28 15:26 ` Arnaldo Carvalho de Melo
2017-09-28 15:58 ` Jiri Olsa
2017-09-28 16:06 ` [PATCH] perf tests attr: Fix group stat tests Jiri Olsa
2017-09-15 18:45 ` Jiri Olsa [this message]
2017-09-18 7:41 ` [PATCH 1/2] perf test attr: fix python error on empty result Thomas-Mich Richter
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=20170915184503.GA31734@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.vnet.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).