From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v2] tracing/x86: Update syscall trace events to handle new x86 syscall func names
Date: Tue, 17 Apr 2018 15:04:30 -0300 [thread overview]
Message-ID: <20180417180430.GF3625@kernel.org> (raw)
In-Reply-To: <20180417172236.GA17342@light.dominikbrodowski.net>
Em Tue, Apr 17, 2018 at 07:22:36PM +0200, Dominik Brodowski escreveu:
> > Added back original compare to not miss 32bit kernel syscalls
>
> s/32bit/32bit and 0-parameter syscalls.
So this should have covered 0-parameter syscalls, ok, I'm double
checking that the last patch is the one I have running... Because
0-parameter syscalls are not working for me, i.e. no
syscalls:sys_enter_getppid, for instance.
- Arnaldo
> Looks good otherwise.
>
> Thanks,
> Dominik
next prev parent reply other threads:[~2018-04-17 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 17:07 [PATCH v2] tracing/x86: Update syscall trace events to handle new x86 syscall func names Steven Rostedt
2018-04-17 17:22 ` Dominik Brodowski
2018-04-17 18:04 ` Arnaldo Carvalho de Melo [this message]
2018-04-17 18:13 ` Arnaldo Carvalho de Melo
2018-04-17 18:16 ` Steven Rostedt
2018-04-17 21:41 ` Steven Rostedt
2018-04-18 12:53 ` Arnaldo Carvalho de Melo
2018-04-18 14:36 ` Steven Rostedt
2018-04-18 15:02 ` Arnaldo Carvalho de Melo
2018-04-18 15:17 ` Arnaldo Carvalho de Melo
2018-04-18 15:20 ` Steven Rostedt
2018-04-18 15:25 ` Arnaldo Carvalho de Melo
2018-04-18 15:30 ` Steven Rostedt
2018-04-18 15:45 ` Steven Rostedt
2018-04-17 17:29 ` Arnaldo Carvalho de Melo
2018-04-17 17:56 ` Arnaldo Carvalho 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=20180417180430.GF3625@kernel.org \
--to=acme@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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