From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo de Melo <acme@redhat.com>,
Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>,
Michael Petlan <mpetlan@redhat.com>,
linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
kernel-team@lge.com
Subject: Re: [PATCH] perf test shell: Fix check open filename arg using 'perf trace'
Date: Fri, 1 Dec 2017 12:16:28 -0300 [thread overview]
Message-ID: <20171201151628.GB3298@kernel.org> (raw)
In-Reply-To: <20171201023314.GC30867@sejong>
Em Fri, Dec 01, 2017 at 11:33:14AM +0900, Namhyung Kim escreveu:
> On Thu, Nov 30, 2017 at 01:56:42PM -0200, Arnaldo de Melo wrote:
> > Em Thu, Nov 30, 2017 at 11:28:33AM +0100, Thomas-Mich Richter escreveu:
> > > On 11/29/2017 06:27 PM, Michael Petlan wrote:
> > > > The commit f231af789b11a2f1a3795acc3228a3e178a80c21 adds an exception for s390x to
> > > > use openat() syscall instead of open(). This exception is not s390x-only, thus I
> > > > adjusted the test to accept both open and openat syscalls, no matter which arch it
> > > > runs on. Does it sound reasonable to you?
> It seems glibc 2.26 changed the behavior:
> https://lwn.net/Articles/738694/
interesting
> > What differs from x86 to others is that x86 uses syscalltbl, not requiring
> > audit-libs to map syscall numbers to names, so perhaps it is something in there...
> If it only needs to consider open or openat, why not specifying the
> both directly?
> # perf trace -e open -e openat touch /etc/passwd
Same effect, works with other perf trace versions, but one suggestion to
make it shorter:
perf trace -e open,openat touch /etc/passwd
Does the same thing :-)
Michael, can you please take that into account and resubmit the patch?
- Arnaldo
next prev parent reply other threads:[~2017-12-01 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 17:27 [PATCH] perf test shell: Fix check open filename arg using 'perf trace' Michael Petlan
2017-11-30 10:28 ` Thomas-Mich Richter
2017-11-30 15:56 ` Arnaldo de Melo
2017-11-30 15:59 ` Arnaldo de Melo
2017-12-05 15:39 ` Hendrik Brueckner
2017-12-06 16:34 ` Arnaldo Carvalho de Melo
2017-12-07 7:39 ` Hendrik Brueckner
2017-12-01 2:33 ` Namhyung Kim
2017-12-01 15:16 ` Arnaldo Carvalho de Melo [this message]
2017-12-02 23:21 ` Michael Petlan
2017-12-05 23:18 ` Michael Petlan
2017-12-06 14:28 ` Arnaldo de Melo
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=20171201151628.GB3298@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@lge.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--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).