From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm: make return_address available for ARM_UNWIND
Date: Thu, 3 Jan 2013 16:23:59 +0000 [thread overview]
Message-ID: <20130103162359.GR2631@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1357229038.10284.46.camel@gandalf.local.home>
On Thu, Jan 03, 2013 at 11:03:58AM -0500, Steven Rostedt wrote:
> On Thu, 2013-01-03 at 14:13 +0000, Russell King - ARM Linux wrote:
> > In summary, from what I can see in the patch, the reason why the ifdefs
> > are the way they are, and the reason the warning is there has not been
> > addressed; these patches just seem to be aimed just at removing a #warning
> > statement to make the warning go away.
>
> You're correct that this patch does not solve any of theses issues. Now,
> I'm thinking that ftrace has matured where these issues don't exist, and
> where they do, it will only cause noise in the trace than anything
> serious. But, this needs to be looked deeper to make sure.
Looking back in the archives, it seems that we had a problem with ftrace
and the unwinder polluting the trace information:
http://lists.arm.linux.org.uk/lurker/message/20090604.201745.1c41ee6c.en.html
There's quite a bit of discussion in that thread about this which details
why we came up with what we have today.
next prev parent reply other threads:[~2013-01-03 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 10:12 [PATCH 1/2] arm: fix returning wrong CALLER_ADDRx kpark3469 at gmail.com
2013-01-03 10:12 ` [PATCH 2/2] arm: make return_address available for ARM_UNWIND kpark3469 at gmail.com
2013-01-03 10:38 ` Russell King - ARM Linux
2013-01-03 11:36 ` Keun-O Park
2013-01-03 13:36 ` Steven Rostedt
2013-01-03 14:13 ` Russell King - ARM Linux
2013-01-03 16:03 ` Steven Rostedt
2013-01-03 16:23 ` Russell King - ARM Linux [this message]
2013-01-03 16:58 ` Steven Rostedt
2013-01-04 8:45 ` Keun-O Park
2013-01-07 13:41 ` Steven Rostedt
2013-01-11 8:53 ` Keun-O Park
2013-01-11 22:04 ` 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=20130103162359.GR2631@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).