[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100327045958.GQ7166@nowhere>
Date: Sat, 27 Mar 2010 06:00:00 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Jason Baron <jbaron@...hat.com>
Cc: mingo@...e.hu, rostedt@...dmis.org, linux-kernel@...r.kernel.org,
laijs@...fujitsu.com, lizf@...fujitsu.com, hpa@...or.com,
tglx@...utronix.de, mhiramat@...hat.com, heiko.carstens@...ibm.com,
benh@...nel.crashing.org, davem@...emloft.net, lethal@...ux-sh.org,
schwidefsky@...ibm.com, brueckner@...ux.vnet.ibm.com,
tony.luck@...el.com
Subject: Re: [PATCH 00/14] tracing: add compat syscall support v3
On Tue, Mar 16, 2010 at 01:46:08PM -0400, Jason Baron wrote:
> Hi,
>
> Re-post to add infrastructure for compat syscall event tracing support. This
> patch series also adds x86_64 arch specific support as an example consumer
> of the new infrastructure.
>
> Arches can request compat syscall tracing by setting:
> __HAVE_ARCH_FTRACE_COMPAT_SYSCALLS, if CONFIG_COMPAT and CONFIG_FTRACE_SYSCALLS
> are set. Arches then need to implement the following interfaces:
>
> 1) int is_compat_task(void);
> - most arches seem to have this already
> 2) unsigned long arch_compat_syscall_addr(int nr);
> - returns a pointer to the compat syscall entry corresponding to syscall 'nr'
> 3) int NR_syscalls_compat;
> - number of entries in the compat syscall table.
>
> thanks,
>
> -Jason
>
> Changes in v3:
>
> - create a separate "compat_syscalls" event subsystem
> - ARCH_COMPAT_SYSCALL_DEFINE#N() tacks "sys32" to start of syscall name
> - COMPAT_SYSCALL_DEFINE#N() tacks "compat_sys" to start of syscall name
> - both above macros create perf events as: [enter|exit]_compat_sys_blah
> - non-compat syscall naming changes to: [enter|exit]_sys_blah
> - removes any unreferenced compat syscalls from debugfs
Other than the small comments I had, it's a very nice stuff.
Just waiting for your next iteration before applying.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists