From: Michael Ellerman <mpe@ellerman.id.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
paulmck@linux.vnet.ibm.com, Andrew Morton <akpm@osdl.org>,
tglx@linutronix.de, mathieu.desnoyers@efficios.com,
xiakaixu@huawei.com
Subject: Re: [PATCH] tracing: Allow raw_syscall tracepoints to work from boot
Date: Thu, 15 Jan 2015 17:10:40 +1100 [thread overview]
Message-ID: <1421302240.11409.6.camel@ellerman.id.au> (raw)
In-Reply-To: <20150114130300.75c5d2ce@gandalf.local.home>
On Wed, 2015-01-14 at 13:03 -0500, Steven Rostedt wrote:
> On Wed, 14 Jan 2015 09:35:17 +1100
> Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > In commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after
> > rcu_init()", tracing was enabled earlier in boot.
> >
> > This broke tracing of the raw_syscall tracepoints from boot using the
> > trace_event kernel parameter.
> >
> > We can fix it by explicitly setting TIF_SYSCALL_TRACEPOINT for the
> > init_task. That way when pid 1 is cloned from init_task it will inherit
> > TIF_SYSCALL_TRACEPOINT.
>
> I don't like setting the swap task flag for syscall tracing, as nothing
> will unset it.
We could unset it in the unregfunc(), I did that in my original patch but took
it out because I wasn't sure it was necessary.
> > It feels a bit naughty to be whacking init_task like this, but it also
> > seems like the right fix?
>
> No, I tried the following instead.
>
> > Should we also clear it in the unregfunc? I can't see how that would
> > ever be needed in practice?
>
> It just seems hacky to set swapper in the first place.
Actually I thought it was neat, basically everything else comes from init_task
via copy_process().
> Try my patch and let me know if it works for you?
Sure. It works.
I can still see the first syscalls in the trace:
# entries-in-buffer/entries-written: 1021354/1021354 #P:8
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
init-1 [000] .... 3.706370: sys_exit: NR -1 = 0
init-1 [000] .... 3.706394: sys_enter: NR 45 (0, 0, 3fffa2e20000, 3fffcfd4eac2, 80, 3fffa2e61820)
init-1 [000] .... 3.706395: sys_exit: NR 45 = 70367490932736
init-1 [000] .... 3.706409: sys_enter: NR 33 (3fffa2e694d0, 0, 3fffa2e7be20, 0, 1, ffffffffe0000000)
init-1 [000] .... 3.713325: sys_exit: NR 33 = -2
I like my version better, but your call.
cheers
next prev parent reply other threads:[~2015-01-15 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 22:35 Michael Ellerman
2015-01-14 18:03 ` Steven Rostedt
2015-01-15 6:10 ` Michael Ellerman [this message]
2015-01-15 13:58 ` Steven Rostedt
2015-01-15 22:47 ` Michael Ellerman
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=1421302240.11409.6.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=xiakaixu@huawei.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
Powered by JetHome