From: Michael Petlan <mpetlan@redhat.com>
To: linux-perf-users@vger.kernel.org
Cc: Arnaldo de Melo <acme@redhat.com>, Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace
Date: Fri, 8 Dec 2017 18:48:17 +0100 (CET) [thread overview]
Message-ID: <alpine.LRH.2.20.1712081845230.9416@Diego> (raw)
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi Arnaldo, so I have tried what you've suggested and looks good.
Patch is attached. Sorry for not posting it in-text, but I need to
fix my mail client first, since it screwes some patches up due to
flowed-text...
Cheers,
Michael
[-- Attachment #2: Type: text/plain, Size: 1785 bytes --]
commit 92281a9ff73f98d8aca7595504340a25c92b9f1a
Author: Michael Petlan <mpetlan@redhat.com>
Date: Fri Dec 8 18:43:18 2017 +0100
perf test shell: Fix check open filename arg using 'perf trace'
The following commit added an exception for s390x to use openat()
instead of open() in the test:
commit f231af789b11a2f1a3795acc3228a3e178a80c21
Author: Thomas Richter <tmricht@linux.vnet.ibm.com>
Date: Tue Nov 14 08:18:46 2017 +0100
Since the problem is not s390x-specific, this patch makes it more
generic, so the test handles both open() and openat() no matter
which architecture it is running on.
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
diff --git a/tools/perf/tests/shell/trace+probe_vfs_getname.sh b/tools/perf/tests/shell/trace+probe_vfs_getname.sh
index 2a9ef08..edd1073 100755
--- a/tools/perf/tests/shell/trace+probe_vfs_getname.sh
+++ b/tools/perf/tests/shell/trace+probe_vfs_getname.sh
@@ -17,10 +17,9 @@ skip_if_no_perf_probe || exit 2
file=$(mktemp /tmp/temporary_file.XXXXX)
trace_open_vfs_getname() {
- test "$(uname -m)" = s390x && { svc="openat"; txt="dfd: +CWD, +"; }
-
- perf trace -e ${svc:-open} touch $file 2>&1 | \
- egrep " +[0-9]+\.[0-9]+ +\( +[0-9]+\.[0-9]+ ms\): +touch\/[0-9]+ ${svc:-open}\(${txt}filename: +${file}, +flags: CREAT\|NOCTTY\|NONBLOCK\|WRONLY, +mode: +IRUGO\|IWUGO\) += +[0-9]+$"
+ evts=`perf list syscalls:sys_enter_open* |& egrep 'open(at)? ' | sed -r 's/.*sys_enter_(.*) +\[.*/-e \1/'`
+ perf trace $evts touch $file 2>&1 | \
+ egrep " +[0-9]+\.[0-9]+ +\( +[0-9]+\.[0-9]+ ms\): +touch\/[0-9]+ open(at)?\((dfd: +CWD, +)?filename: +${file}, +flags: CREAT\|NOCTTY\|NONBLOCK\|WRONLY, +mode: +IRUGO\|IWUGO\) += +[0-9]+$"
}
next reply other threads:[~2017-12-08 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 17:48 Michael Petlan [this message]
2017-12-11 15:43 ` [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace Arnaldo de Melo
2017-12-11 17:07 ` Arnaldo Carvalho de Melo
2017-12-12 3:05 ` Michael Petlan
2017-12-12 14:57 ` Arnaldo Carvalho de Melo
2017-12-12 15:19 ` Arnaldo Carvalho de Melo
2017-12-12 16:24 ` Michael Petlan
2017-12-12 17:12 ` Arnaldo Carvalho de Melo
2017-12-14 12:08 ` Thomas-Mich Richter
2017-12-14 14:03 ` Arnaldo Carvalho de Melo
2017-12-12 16:30 ` Michael Petlan
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=alpine.LRH.2.20.1712081845230.9416@Diego \
--to=mpetlan@redhat.com \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@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