From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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, Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] tracing/x86: Update syscall trace events to handle new x86 syscall func names
Date: Tue, 17 Apr 2018 18:58:43 +0200 [thread overview]
Message-ID: <20180417165843.GA14271@light.dominikbrodowski.net> (raw)
In-Reply-To: <20180417123927.4406f990@gandalf.local.home>
On Tue, Apr 17, 2018 at 12:39:27PM -0400, Steven Rostedt wrote:
> > > names, they do not match the default compare algorithm. As this was a
> > > problem for power pc, the algorithm can be overwritten by the architecture.
> > > The solution is to have x86 have its own algorithm to do the compare and
> > > this brings back the system call trace events.
> >
> > this lets me wonder *which* syscall "function" should be included in this
> > directory. Is it really the stub (__x64_sys_waitid, for example), or better
> > the sign-extending C function (__se_sys_waitid) which then calls an
> > internal helper (__do_sys_waitid). An additional advantage:
> > __se_sys_waitid would be available on x86 and, AFAICS, on all other archs.
>
> It should include anything that uses the "SYSCALL_DEFINE#()" macros.
Well, that's not a 1:1, but a 1:several translation... SYSCALL_DEFINEx()
[SYSCALL_DEFINE0() is special] expands to
__do_sys_waitid # inlined helper doing actual work
__se_sys_waitid # C func calling inlined helper
on all architectures, with most (!= 64-bit x86) also having
sys_waitid # alias to __se_sys_waitid()
On 64-bit x86, it does not only extend to the two functions mentioned above,
but also to one or two stubs (depending on the configuration), namely
__x64_sys_waitid # x64 64-bit-ptregs -> C stub
__ia32_sys_waitid # ia32 32-bit-ptregs -> C stub
Thanks,
Dominik
next prev parent reply other threads:[~2018-04-17 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:54 Steven Rostedt
2018-04-17 16:10 ` Dominik Brodowski
2018-04-17 16:39 ` Steven Rostedt
2018-04-17 16:58 ` Dominik Brodowski [this message]
2018-04-17 16:35 ` Arnaldo Carvalho de Melo
2018-04-17 16:40 ` Steven Rostedt
2018-04-17 16:44 ` Arnaldo Carvalho de Melo
2018-04-17 16:57 ` Steven Rostedt
2018-04-17 17:06 ` Arnaldo Carvalho de Melo
2018-04-17 17:08 ` Arnaldo Carvalho de Melo
2018-04-17 17:10 ` Steven Rostedt
2018-04-17 17:10 ` 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=20180417165843.GA14271@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=acme@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®