From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vaibhav Nagarnaik <vnagarnaik@google.com>
Subject: Re: [RFC][PATCH v2] tracing/syscalls: Allow archs to ignore tracing compat syscalls
Date: Tue, 12 Feb 2013 16:42:04 -0500 [thread overview]
Message-ID: <1360705324.21867.100.camel@gandalf.local.home> (raw)
In-Reply-To: <511AB525.4050300@linux.intel.com>
On Tue, 2013-02-12 at 13:33 -0800, H. Peter Anvin wrote:
> On 02/12/2013 01:18 PM, Steven Rostedt wrote:
> > [
> > Peter, how about this patch. Instead of showing garbage, just never
> > trace compat syscalls, if the arch needs to ignore it.
> >
> > However, users can still use the raw_syscall interface if they need to
> > trace them.
> > ]
> >
>
> I can go for that. At least it doesn't make the current situation any
> messier than it currently is, and it prevents incorrect information from
> being output.
>
Great, can I have your Acked-by. Then I'll start testing it and get it
ready to push for 3.9.
-- Steve
next prev parent reply other threads:[~2013-02-12 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 18:01 [RFC][PATCH] tracing/syscalls: Have ia32 compat syscalls show raw format Steven Rostedt
2013-02-12 18:11 ` H. Peter Anvin
2013-02-12 18:42 ` Steven Rostedt
2013-02-12 18:51 ` Steven Rostedt
2013-02-12 19:39 ` H. Peter Anvin
2013-02-12 19:54 ` H. Peter Anvin
2013-02-12 21:18 ` [RFC][PATCH v2] tracing/syscalls: Allow archs to ignore tracing compat syscalls Steven Rostedt
2013-02-12 21:33 ` H. Peter Anvin
2013-02-12 21:42 ` Steven Rostedt [this message]
2013-02-12 22:34 ` H. Peter Anvin
2013-02-20 13:55 ` [tip:perf/urgent] " tip-bot for Steven Rostedt
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=1360705324.21867.100.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=vnagarnaik@google.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;
as well as URLs for NNTP newsgroup(s).