From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jason Baron <jbaron@redhat.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Jiaying Zhang <jiayingz@google.com>,
Martin Bligh <mbligh@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: [GIT PULL] tracing/syscalls: The next bunch
Date: Sun, 30 Aug 2009 01:33:06 +0200 [thread overview]
Message-ID: <20090829233304.GA6101@nowhere> (raw)
In-Reply-To: <20090829104334.GA17156@elte.hu>
On Sat, Aug 29, 2009 at 12:43:34PM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > Ingo,
> >
> > Here is another bunch of syscalls tracing patches.
>
> i have tested them, and something in this batch, when merged into
> tip/master:
>
> 0dd7b74: tracing: Fix double CPP substitution in TRACE_EVENT_FN
> 66c6e29: Merge branch 'tracing/core' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing into tracing/core
> 117226d: tracing: Remove FTRACE_SYSCALL_MAX definitions
> 57421db: tracing: Convert event tracing code to use NR_syscalls
> a5a2f8e: tracing: Define NR_syscalls for x86_64
> dd86dda: tracing: Define NR_syscalls for x86 (32)
> cc3b13c: tracing: Don't trace kernel thread syscalls
> cd0980f: tracing: Check invalid syscall nr while tracing syscalls
> 7515bf5: tracing: Add syscall tracepoints - s390 arch update
Argh, I've just tested a merge of tip:tracing/core into tip:master
and I can't reproduce the hang, neither in x86-64 SMP nor in a
pentium III :-(
next prev parent reply other threads:[~2009-08-29 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 17:43 [GIT PULL] tracing/syscalls: The next bunch Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 1/7] tracing: Add syscall tracepoints - s390 arch update Frederic Weisbecker
2009-08-27 17:50 ` Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 2/7] tracing: Check invalid syscall nr while tracing syscalls Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 3/7] tracing: Don't trace kernel thread syscalls Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 4/7] tracing: Define NR_syscalls for x86 (32) Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 5/7] tracing: Define NR_syscalls for x86_64 Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 6/7] tracing: Convert event tracing code to use NR_syscalls Frederic Weisbecker
2009-08-27 17:43 ` [PATCH 7/7] tracing: Remove FTRACE_SYSCALL_MAX definitions Frederic Weisbecker
2009-08-29 10:43 ` [GIT PULL] tracing/syscalls: The next bunch Ingo Molnar
2009-08-29 23:33 ` Frederic Weisbecker [this message]
2009-08-31 8:35 ` Ingo Molnar
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=20090829233304.GA6101@nowhere \
--to=fweisbec@gmail.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=laijs@cn.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.