From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Call tracing/debug code in VFP preempt code
Date: Mon, 4 Mar 2013 14:43:01 -0800 [thread overview]
Message-ID: <1362436983-28988-1-git-send-email-sboyd@codeaurora.org> (raw)
The VFP preempt enable/disable code doesn't call into the tracers
and also doesn't participate in the preempt debugging code. This
patchset fixes that by making calls to the C functions from assembly
when appropriate.
Stephen Boyd (2):
ARM: Consolidate preempt enable/disable assembly into macros
ARM: Enable tracing around vfp preemption enable/disable
arch/arm/kernel/entry-header.S | 31 +++++++++++++++++++++++++++++++
arch/arm/vfp/entry.S | 20 +++-----------------
arch/arm/vfp/vfphw.S | 14 ++------------
3 files changed, 36 insertions(+), 29 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2013-03-04 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 22:43 Stephen Boyd [this message]
2013-03-04 22:43 ` [PATCH 1/2] ARM: Consolidate preempt enable/disable assembly into macros Stephen Boyd
2013-03-04 22:43 ` [PATCH 2/2] ARM: Enable tracing around vfp preemption enable/disable Stephen Boyd
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=1362436983-28988-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.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 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).