From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, rostedt@goodmis.org,
k-keiichi@bx.jp.nec.com
Subject: Re: [PATCH 08/12] perf: export some syscall metadata
Date: Tue, 23 Feb 2010 22:44:51 +0100 [thread overview]
Message-ID: <20100223214445.GF5357@nowhere> (raw)
In-Reply-To: <1264580883-15324-9-git-send-email-tzanussi@gmail.com>
On Wed, Jan 27, 2010 at 02:27:59AM -0600, Tom Zanussi wrote:
> Create and export a list of syscall_nr:syscall_name pairs from the
> data in the syscalls_metadata, for use initially by perf trace.
>
> Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
I would have much more preferred we inject a kind of "syscall_map"
event for that. Unfortunately the event injection is still
in discussion and not yet ready.
I guess we can take this temporary solution and remove that
later in profit of injected events. It means we'll need to
keep support for that file though.
Hmm...
> ---
> kernel/trace/trace_syscalls.c | 87 +++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 87 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
> index f6b0712..e037486 100644
> --- a/kernel/trace/trace_syscalls.c
> +++ b/kernel/trace/trace_syscalls.c
> @@ -626,5 +626,92 @@ void prof_sysexit_disable(struct ftrace_event_call *call)
> mutex_unlock(&syscall_trace_lock);
> }
>
> +struct syscall_metadata **meta_skip(struct syscall_metadata **meta,
> + loff_t *pos)
> +{
> + struct syscall_metadata **end = syscalls_metadata + NR_syscalls;
> +
> + do {
> + meta++;
> + (*pos)++;
> + } while (meta < end && *meta == NULL);
> +
> + if (meta >= end)
> + meta = NULL;
> +
> + return meta;
> +}
> +
> +static void *syscall_map_start(struct seq_file *s, loff_t *pos)
> +{
> + struct syscall_metadata **end = syscalls_metadata + NR_syscalls;
> + struct syscall_metadata **meta = syscalls_metadata + *pos;
> +
> + if (meta >= end)
> + return NULL;
> +
> + if (*meta == NULL)
> + meta = meta_skip(meta, pos);
> +
> + return meta;
> +}
> +
> +static void *syscall_map_next(struct seq_file *s, void *v, loff_t *pos)
> +{
> + (*pos)++;
> +
> + return syscall_map_start(s, pos);
> +}
> +
> +static int syscall_map_show(struct seq_file *s, void *v)
> +{
> + const struct syscall_metadata **meta = v;
> + const struct syscall_metadata *m = *meta;
> +
> + seq_printf(s, "%d:", m->syscall_nr);
> + seq_printf(s, "%s\n", m->name);
> +
> + return 0;
> +}
> +
> +static void syscall_map_stop(struct seq_file *m, void *p)
> +{
> +}
> +
> +static const struct seq_operations show_syscall_map_seq_ops = {
> + .start = syscall_map_start,
> + .next = syscall_map_next,
> + .show = syscall_map_show,
> + .stop = syscall_map_stop,
> +};
> +
> +static int syscall_map_open(struct inode *inode, struct file *file)
> +{
> + return seq_open(file, &show_syscall_map_seq_ops);
> +}
> +
> +static const struct file_operations syscall_map_fops = {
> + .open = syscall_map_open,
> + .read = seq_read,
> + .llseek = seq_lseek,
> + .release = seq_release,
> +};
> +
> +static __init int init_syscall_map(void)
> +{
> + struct dentry *d_tracer;
> +
> + d_tracer = tracing_init_dentry();
> + if (!d_tracer)
> + return 0;
> +
> + trace_create_file("syscall_map", 0444, d_tracer,
> + NULL, &syscall_map_fops);
> +
> + return 0;
> +}
> +
> +fs_initcall(init_syscall_map);
> +
> #endif /* CONFIG_PERF_EVENTS */
>
> --
> 1.6.4.GIT
>
next prev parent reply other threads:[~2010-02-23 21:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 8:27 [PATCH 00/12] perf trace: Python scripting support Tom Zanussi
2010-01-27 8:27 ` [PATCH 01/12] perf trace/scripting: Fix supported language listing option Tom Zanussi
2010-02-25 10:06 ` [tip:perf/core] perf/scripts: " tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 02/12] perf trace/scripting: fix bug in Util.pm Tom Zanussi
2010-02-25 10:06 ` [tip:perf/core] perf/scripts: Fix " tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 03/12] perf trace/scripting: move common code out of Perl-specific files Tom Zanussi
2010-02-25 10:07 ` [tip:perf/core] perf/scripts: Move " tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 04/12] perf trace/scripting: move Perl scripting files to scripting-engines dir Tom Zanussi
2010-02-25 10:07 ` [tip:perf/core] perf/scripts: Move " tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 05/12] perf trace/scripting: remove check-perf-trace from listed scripts Tom Zanussi
2010-02-22 1:51 ` Frederic Weisbecker
2010-02-25 10:07 ` [tip:perf/core] perf/scripts: Remove " tip-bot for Tom Zanussi
2010-02-25 10:07 ` [tip:perf/core] perf/scripts: Add Python scripting engine tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 06/12] perf trace/scripting: add " Tom Zanussi
2010-02-22 2:27 ` Frederic Weisbecker
2010-02-22 7:12 ` Tom Zanussi
2010-02-25 10:08 ` [tip:perf/core] perf/scripts: Remove unnecessary PyTuple resizes tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 07/12] perf trace/scripting: add syscall tracing scripts Tom Zanussi
2010-02-25 10:08 ` [tip:perf/core] perf/scripts: Add " tip-bot for Tom Zanussi
2010-01-27 8:27 ` [PATCH 08/12] perf: export some syscall metadata Tom Zanussi
2010-02-23 21:44 ` Frederic Weisbecker [this message]
2010-02-24 6:00 ` Tom Zanussi
2010-02-25 1:52 ` Frederic Weisbecker
2010-02-25 6:09 ` Tom Zanussi
2010-02-25 2:43 ` Frederic Weisbecker
2010-02-25 6:51 ` Tom Zanussi
2010-03-27 0:37 ` Frederic Weisbecker
2010-03-28 5:18 ` Tom Zanussi
2010-01-27 8:28 ` [PATCH 09/12] perf tools: save syscall map Tom Zanussi
2010-01-27 8:28 ` [PATCH 10/12] perf trace/scripting: make the syscall map available as a Python dict Tom Zanussi
2010-01-27 8:28 ` [PATCH 11/12] perf trace/scripting: make the syscall map available as a Perl hash Tom Zanussi
2010-01-27 8:28 ` [PATCH 12/12] perf trace/scripting: add perf-trace-python Documentation Tom Zanussi
2010-02-25 1:37 ` Frederic Weisbecker
2010-02-25 6:06 ` Tom Zanussi
2010-02-25 10:08 ` [tip:perf/core] perf/scripts: Add " tip-bot for Tom Zanussi
2010-02-19 21:37 ` [PATCH 00/12] perf trace: Python scripting support Frederic Weisbecker
2010-02-20 21:51 ` Tom Zanussi
2010-02-23 17:31 ` Frederic Weisbecker
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=20100223214445.GF5357@nowhere \
--to=fweisbec@gmail.com \
--cc=k-keiichi@bx.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.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