From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: mcpm: Make all mcpm functions notrace
Date: Fri, 14 Feb 2014 11:52:01 +0000 [thread overview]
Message-ID: <1392378721.3475.12.camel@linaro1.home> (raw)
In-Reply-To: <alpine.LFD.2.11.1402131542120.17677@knanqh.ubzr>
On Thu, 2014-02-13 at 15:42 -0500, Nicolas Pitre wrote:
> On Thu, 13 Feb 2014, Jon Medhurst (Tixy) wrote:
>
> > From: Dave Martin <dave.martin@linaro.org>
> >
> > The functions in mcpm_entry.c are mostly intended for use during
> > scary cache and coherency disabling sequences, or do other things
> > which confuse trace ... like powering a CPU down and not
> > returning. Similarly for the backend code.
> >
> > For simplicity, this patch just makes whole files notrace.
> > There should be more than enough traceable points on the paths to
> > these functions, but we can be more fine-grained later if there is
> > a need for it.
> >
> > Signed-off-by: Dave Martin <dave.martin@linaro.org>
> >
> > Also added spc.o to the list of files as it contains functions used by
> > MCPM code which have comments comments like: "might be used in code
> > paths where normal cacheable locks are not working"
> >
> > Signed-off-by: Jon Medhurst <tixy@linaro.org>
>
> Acked-by: Nicolas Pitre <nico@linaro.org>
>
> Please send to RMK's patch system.
Thanks, added as patch 7962/2 [1]. (My first attempt accidentally
omitted the "From: Dave Martin" line - I hope the patch system
understands such lines).
[1] http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7962/2
--
Tixy
next prev parent reply other threads:[~2014-02-14 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:26 [PATCH RESEND] ARM: mcpm: Make all mcpm functions notrace Jon Medhurst (Tixy)
2014-02-13 20:42 ` Nicolas Pitre
2014-02-14 11:52 ` Jon Medhurst (Tixy) [this message]
2014-02-14 13:57 ` Dave Martin
2014-02-14 14:33 ` Sudeep Holla
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=1392378721.3475.12.camel@linaro1.home \
--to=tixy@linaro.org \
--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 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.