From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] arm64: enable context tracking
Date: Thu, 22 May 2014 16:29:19 -0400 [thread overview]
Message-ID: <537E5E1F.3050605@codeaurora.org> (raw)
In-Reply-To: <1400786855-32656-3-git-send-email-larry.bassel@linaro.org>
Hi Larry,
On 05/22/2014 03:27 PM, Larry Bassel wrote:
> Make calls to ct_user_enter when the kernel is exited
> and ct_user_exit when the kernel is entered (in el0_da,
> el0_ia, el0_svc, el0_irq and all of the "error" paths).
>
> These macros expand to function calls which will only work
> properly if el0_sync and related code has been rearranged
> (in a previous patch of this series).
>
> The calls to ct_user_exit are made after hw debugging has been
> enabled (enable_dbg_and_irq).
>
> The call to ct_user_enter is made at the beginning of the
> kernel_exit macro.
>
> This patch is based on earlier work by Kevin Hilman.
> Save/restore optimizations were also done by Kevin.
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
> @@ -30,6 +30,44 @@
> #include <asm/unistd32.h>
>
> /*
> + * Context tracking subsystem. Used to instrument transitions
> + * between user and kernel mode.
> + */
> + .macro ct_user_exit, restore = 0
> +#ifdef CONFIG_CONTEXT_TRACKING
> + bl context_tracking_user_exit
> + .if \restore == 1
> + /*
> + * Save/restore needed during syscalls. Restore syscall arguments from
> + * the values already saved on stack during kernel_entry.
> + */
> + ldp x0, x1, [sp]
> + ldp x2, x3, [sp, #S_X2]
> + ldp x4, x5, [sp, #S_X4]
> + ldp x6, x7, [sp, #S_X6]
> + .endif
> +#endif
> + .endm
> +
> + .macro ct_user_enter, save = 0
> +#ifdef CONFIG_CONTEXT_TRACKING
> + .if \save == 1
> + /*
> + * Save/restore only needed on syscall fastpath, which uses
> + * x0-x2.
> + */
> + push x2, x3
Why is x3 saved?
> + push x0, x1
> + .endif
> + bl context_tracking_user_enter
> + .if \save == 1
> + pop x0, x1
> + pop x2, x3
> + .endif
> +#endif
> + .endm
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-05-22 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 19:27 [PATCH v4 0/2] context tracker support for arm64 Larry Bassel
2014-05-22 19:27 ` [PATCH v4 1/2] arm64: adjust el0_sync so that a function can be called Larry Bassel
2014-05-22 20:23 ` Christopher Covington
2014-05-22 22:35 ` Larry Bassel
2014-05-23 14:44 ` Catalin Marinas
2014-05-23 17:04 ` Larry Bassel
2014-05-22 19:27 ` [PATCH v4 2/2] arm64: enable context tracking Larry Bassel
2014-05-22 20:29 ` Christopher Covington [this message]
2014-05-23 0:11 ` Kevin Hilman
2014-05-23 14:51 ` Catalin Marinas
2014-05-23 15:55 ` Mark Rutland
2014-05-23 16:12 ` Will Deacon
2014-05-24 0:03 ` Kevin Hilman
2014-05-22 20:19 ` [PATCH v4 0/2] context tracker support for arm64 Kevin Hilman
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=537E5E1F.3050605@codeaurora.org \
--to=cov@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).