From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Annotate irq functions with "notrace"
Date: Mon, 26 Oct 2009 22:57:34 +0000 [thread overview]
Message-ID: <20091026225734.GC16759@linux-sh.org> (raw)
In-Reply-To: <1256595589-15800-1-git-send-email-matt@console-pimps.org>
On Mon, Oct 26, 2009 at 10:49:40PM +0000, Matt Fleming wrote:
> On Tue, Oct 27, 2009 at 07:38:23AM +0900, Paul Mundt wrote:
> > On Mon, Oct 26, 2009 at 10:19:49PM +0000, Matt Fleming wrote:
> > > Now that SH's irqflags functions are out of line it becomes necessary to
> > > mark them as "notrace" so that we don't try to trace them.
> > >
> > > Signed-off-by: Matt Fleming <matt@console-pimps.org>
> >
> > This applies for the _64 bits too, but I just did those by hand.
> >
> > Applied, thanks.
>
> Ah, doh. I didn't realise that tracing worked for SUPERH64.
It doesn't yet, but we like to do future proofing, especially when the
issue at hand is fresh in ones mind. Otherwise we run in to situations
where when a feature is finally carried over, all of the subtle fixes
that came along with it are long forgotten and much debugging ensues.
Also note that notrace in itself has more implications than simply
tracing, it explicitly disables instrumentation. So it also matters
in the mcount case. If it were only the function graph tracer that were
problematic (as in the case of __switch_to) we would use __notrace_funcgraph,
which is much more explicitly stated.
prev parent reply other threads:[~2009-10-26 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 22:19 [PATCH] sh: Annotate irq functions with "notrace" Matt Fleming
2009-10-26 22:38 ` Paul Mundt
2009-10-26 22:49 ` Matt Fleming
2009-10-26 22:57 ` Paul Mundt [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=20091026225734.GC16759@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.