From: Steven Rostedt <rostedt@goodmis.org>
To: Torsten Duwe <duwe@lst.de>
Cc: Denis Kirjanov <kda@linux-powerpc.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Jiri Kosina <jkosina@suse.cz>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 0/4] ppc64 LE ABI v2 ftrace-with-regs implementation
Date: Fri, 19 Jun 2015 08:41:49 -0400 [thread overview]
Message-ID: <20150619084149.1c625bf8@grimm.local.home> (raw)
In-Reply-To: <20150619121703.GC3805@lst.de>
On Fri, 19 Jun 2015 14:17:03 +0200
Torsten Duwe <duwe@lst.de> wrote:
> On Fri, Jun 19, 2015 at 10:15:44AM +0300, Denis Kirjanov wrote:
> >
> > Hi Torsten,
> >
> > could you provide a description how you did test that.
>
> Vanilla kernel, those patches on top, built as described to
> Steven in the previous mail (.config attached there, built
> natively on ppc64le ABIv2, mentioned tool versions)
>
Great that you got it working on your machine. But you need to do it in
a way that you don't break builds of existing machines, with existing
(still supported) compilers.
-- Steve
> make vmlinux, make modules, build initrd
> qemu-system-ppc64 -no-reboot -enable-kvm -m 20480 -kernel vmlinux
> -initrd initrd.gz -append console=hvc0 -nographic -vga none
> inside:
> cd /sys/kernel/debug/tracing
> mkdir instances/Foo
> cd instances/Foo
> echo function > current_tracer
>
> current_tracer holds "nop" or "function"; the transition is accompanied
> by heavy binary patching. When the function tracer is active, almost all
> calls go through ftrace_caller. This should be enough for a start; the
> proper stack frame layout details for the tracer functions still remain
> to be checked...
>
> Torsten
prev parent reply other threads:[~2015-06-19 12:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 9:53 [PATCH 0/4] resend: ppc64 LE ABI v2 ftrace-with-regs implementation Torsten Duwe
2015-06-11 9:58 ` [PATCH 1/4] ppc64 FTRACE_WITH_REGS implementation Torsten Duwe
2015-06-11 9:59 ` [PATCH 2/4] ppc64 ftrace_with_regs configuration variables Torsten Duwe
2015-06-11 10:01 ` [PATCH 3/4] ppc64 ftrace_with_regs: spare early boot and low level code Torsten Duwe
2015-06-11 10:03 ` [PATCH 4/4] ppc64 ftrace_with_regs recursion protection Torsten Duwe
2015-06-18 16:17 ` [RESEND PATCH 0/4] ppc64 LE ABI v2 ftrace-with-regs implementation Torsten Duwe
2015-06-18 16:21 ` [RESEND PATCH 1/4] ppc64 FTRACE_WITH_REGS implementation Torsten Duwe
2015-06-18 16:49 ` Steven Rostedt
2015-06-19 12:01 ` Torsten Duwe
2015-06-19 13:26 ` Steven Rostedt
2015-06-18 16:22 ` [RESEND PATCH 2/4] ppc64 ftrace_with_regs configuration variables Torsten Duwe
2015-06-18 16:24 ` [RESEND PATCH 3/4] ppc64 ftrace_with_regs: spare early boot and low level code Torsten Duwe
2015-06-18 16:25 ` [RESEND PATCH 4/4] ppc64 ftrace_with_regs recursion protection Torsten Duwe
2015-06-18 16:55 ` [RESEND PATCH 0/4] ppc64 LE ABI v2 ftrace-with-regs implementation Steven Rostedt
2015-06-19 12:00 ` Torsten Duwe
2015-06-19 12:40 ` Steven Rostedt
2015-06-19 13:18 ` Torsten Duwe
2015-06-19 2:49 ` Michael Ellerman
2015-06-19 7:15 ` Denis Kirjanov
2015-06-19 12:17 ` Torsten Duwe
2015-06-19 12:41 ` Steven Rostedt [this message]
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=20150619084149.1c625bf8@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=duwe@lst.de \
--cc=jkosina@suse.cz \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).