From: Andreas Schwab <schwab@linux-m68k.org>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: linux-m68k@vger.kernel.org,
uClinux development list <uclinux-dev@uclinux.org>,
Steven Rostedt <rostedt@goodmis.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: Event tracing support on m68k
Date: Mon, 22 Oct 2012 16:36:39 +0200 [thread overview]
Message-ID: <m2sj96zi88.fsf@igel.home> (raw)
In-Reply-To: <CALF0-+W9ZZNW-ciRyk64WqsSwXVXHjVaFRC563XHN1--S+=Zgw@mail.gmail.com> (Ezequiel Garcia's message of "Mon, 22 Oct 2012 11:22:32 -0300")
Ezequiel Garcia <elezegarcia@gmail.com> writes:
> While trying to trace an m68k (without MMU) platform, I discovered
> there's no "TRACING"
> option on m68k menuconfig.
>
> * Am I doing anything wrong? Is there no tracing support on m68k?
>From Documentation/trace/ftrace-design.txt:
Prerequisites
-------------
Ftrace relies on these features being implemented:
STACKTRACE_SUPPORT - implement save_stack_trace()
TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
next prev parent reply other threads:[~2012-10-22 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 14:22 Event tracing support on m68k Ezequiel Garcia
2012-10-22 14:36 ` Andreas Schwab [this message]
2012-10-22 14:53 ` Ezequiel Garcia
2012-10-22 15:26 ` Andreas Schwab
2012-10-23 1:24 ` Greg Ungerer
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=m2sj96zi88.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=elezegarcia@gmail.com \
--cc=linux-m68k@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.com \
--cc=uclinux-dev@uclinux.org \
/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).