From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] arm64: enable context tracking
Date: Thu, 22 May 2014 17:11:38 -0700 [thread overview]
Message-ID: <7hd2f5icat.fsf@paris.lan> (raw)
In-Reply-To: <537E5E1F.3050605@codeaurora.org> (Christopher Covington's message of "Thu, 22 May 2014 16:29:19 -0400")
+Mark Rutland
Christopher Covington <cov@codeaurora.org> writes:
> 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?
I'll respond here since I worked with Larry on the context save/restore
part.
[insert rather embarassing disclamer of ignorance of arm64 assembly]
Based on my reading of the code, I figured only x0-x2 needed to be
saved. However, based on some experiments with intentionally clobbering
the registers[1] (as suggested by Mark Rutland) in order to make sure
we're saving/restoring the right things, I discovered x3 was needed too
(I missed updating the comment to mention x0-x3.)
Maybe Will/Catalin/Mark R. can shed some light here?
Kevin
[1]
>From 8a8702b4d597d08def22221368beae5db2f4a8aa Mon Sep 17 00:00:00 2001
From: Kevin Hilman <khilman@linaro.org>
Date: Fri, 9 May 2014 13:37:43 -0700
Subject: [PATCH] KJH: test: clobber regs
---
arch/arm64/kernel/entry.S | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
index 520da4c02ece..232f0200e88d 100644
--- a/arch/arm64/kernel/entry.S
+++ b/arch/arm64/kernel/entry.S
@@ -36,6 +36,25 @@
.macro ct_user_exit, restore = 0
#ifdef CONFIG_CONTEXT_TRACKING
bl context_tracking_user_exit
+ movz x0, #0xff, lsl #48
+ movz x1, #0xff, lsl #48
+ movz x2, #0xff, lsl #48
+ movz x3, #0xff, lsl #48
+ movz x4, #0xff, lsl #48
+ movz x5, #0xff, lsl #48
+ movz x6, #0xff, lsl #48
+ movz x7, #0xff, lsl #48
+ movz x8, #0xff, lsl #48
+ movz x9, #0xff, lsl #48
+ movz x10, #0xff, lsl #48
+ movz x11, #0xff, lsl #48
+ movz x12, #0xff, lsl #48
+ movz x13, #0xff, lsl #48
+ movz x14, #0xff, lsl #48
+ movz x15, #0xff, lsl #48
+ movz x16, #0xff, lsl #48
+ movz x17, #0xff, lsl #48
+ movz x18, #0xff, lsl #48
.if \restore == 1
/*
* Save/restore needed during syscalls. Restore syscall arguments from
@@ -60,6 +79,25 @@
push x0, x1
.endif
bl context_tracking_user_enter
+ movz x0, #0xff, lsl #48
+ movz x1, #0xff, lsl #48
+ movz x2, #0xff, lsl #48
+ movz x3, #0xff, lsl #48
+ movz x4, #0xff, lsl #48
+ movz x5, #0xff, lsl #48
+ movz x6, #0xff, lsl #48
+ movz x7, #0xff, lsl #48
+ movz x8, #0xff, lsl #48
+ movz x9, #0xff, lsl #48
+ movz x10, #0xff, lsl #48
+ movz x11, #0xff, lsl #48
+ movz x12, #0xff, lsl #48
+ movz x13, #0xff, lsl #48
+ movz x14, #0xff, lsl #48
+ movz x15, #0xff, lsl #48
+ movz x16, #0xff, lsl #48
+ movz x17, #0xff, lsl #48
+ movz x18, #0xff, lsl #48
.if \save == 1
pop x0, x1
pop x2, x3
--
1.9.2
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: Larry Bassel <larry.bassel@linaro.org>,
catalin.marinas@arm.com, will.deacon@arm.com,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com
Subject: Re: [PATCH v4 2/2] arm64: enable context tracking
Date: Thu, 22 May 2014 17:11:38 -0700 [thread overview]
Message-ID: <7hd2f5icat.fsf@paris.lan> (raw)
In-Reply-To: <537E5E1F.3050605@codeaurora.org> (Christopher Covington's message of "Thu, 22 May 2014 16:29:19 -0400")
+Mark Rutland
Christopher Covington <cov@codeaurora.org> writes:
> 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?
I'll respond here since I worked with Larry on the context save/restore
part.
[insert rather embarassing disclamer of ignorance of arm64 assembly]
Based on my reading of the code, I figured only x0-x2 needed to be
saved. However, based on some experiments with intentionally clobbering
the registers[1] (as suggested by Mark Rutland) in order to make sure
we're saving/restoring the right things, I discovered x3 was needed too
(I missed updating the comment to mention x0-x3.)
Maybe Will/Catalin/Mark R. can shed some light here?
Kevin
[1]
>From 8a8702b4d597d08def22221368beae5db2f4a8aa Mon Sep 17 00:00:00 2001
From: Kevin Hilman <khilman@linaro.org>
Date: Fri, 9 May 2014 13:37:43 -0700
Subject: [PATCH] KJH: test: clobber regs
---
arch/arm64/kernel/entry.S | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
index 520da4c02ece..232f0200e88d 100644
--- a/arch/arm64/kernel/entry.S
+++ b/arch/arm64/kernel/entry.S
@@ -36,6 +36,25 @@
.macro ct_user_exit, restore = 0
#ifdef CONFIG_CONTEXT_TRACKING
bl context_tracking_user_exit
+ movz x0, #0xff, lsl #48
+ movz x1, #0xff, lsl #48
+ movz x2, #0xff, lsl #48
+ movz x3, #0xff, lsl #48
+ movz x4, #0xff, lsl #48
+ movz x5, #0xff, lsl #48
+ movz x6, #0xff, lsl #48
+ movz x7, #0xff, lsl #48
+ movz x8, #0xff, lsl #48
+ movz x9, #0xff, lsl #48
+ movz x10, #0xff, lsl #48
+ movz x11, #0xff, lsl #48
+ movz x12, #0xff, lsl #48
+ movz x13, #0xff, lsl #48
+ movz x14, #0xff, lsl #48
+ movz x15, #0xff, lsl #48
+ movz x16, #0xff, lsl #48
+ movz x17, #0xff, lsl #48
+ movz x18, #0xff, lsl #48
.if \restore == 1
/*
* Save/restore needed during syscalls. Restore syscall arguments from
@@ -60,6 +79,25 @@
push x0, x1
.endif
bl context_tracking_user_enter
+ movz x0, #0xff, lsl #48
+ movz x1, #0xff, lsl #48
+ movz x2, #0xff, lsl #48
+ movz x3, #0xff, lsl #48
+ movz x4, #0xff, lsl #48
+ movz x5, #0xff, lsl #48
+ movz x6, #0xff, lsl #48
+ movz x7, #0xff, lsl #48
+ movz x8, #0xff, lsl #48
+ movz x9, #0xff, lsl #48
+ movz x10, #0xff, lsl #48
+ movz x11, #0xff, lsl #48
+ movz x12, #0xff, lsl #48
+ movz x13, #0xff, lsl #48
+ movz x14, #0xff, lsl #48
+ movz x15, #0xff, lsl #48
+ movz x16, #0xff, lsl #48
+ movz x17, #0xff, lsl #48
+ movz x18, #0xff, lsl #48
.if \save == 1
pop x0, x1
pop x2, x3
--
1.9.2
next prev parent reply other threads:[~2014-05-23 0:11 UTC|newest]
Thread overview: 28+ 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 ` 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 19:27 ` Larry Bassel
2014-05-22 20:23 ` Christopher Covington
2014-05-22 20:23 ` Christopher Covington
2014-05-22 22:35 ` Larry Bassel
2014-05-22 22:35 ` Larry Bassel
2014-05-23 14:44 ` Catalin Marinas
2014-05-23 14:44 ` Catalin Marinas
2014-05-23 17:04 ` Larry Bassel
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 19:27 ` Larry Bassel
2014-05-22 20:29 ` Christopher Covington
2014-05-22 20:29 ` Christopher Covington
2014-05-23 0:11 ` Kevin Hilman [this message]
2014-05-23 0:11 ` Kevin Hilman
2014-05-23 14:51 ` Catalin Marinas
2014-05-23 14:51 ` Catalin Marinas
2014-05-23 15:55 ` Mark Rutland
2014-05-23 15:55 ` Mark Rutland
2014-05-23 16:12 ` Will Deacon
2014-05-23 16:12 ` Will Deacon
2014-05-24 0:03 ` Kevin Hilman
2014-05-24 0:03 ` Kevin Hilman
2014-05-22 20:19 ` [PATCH v4 0/2] context tracker support for arm64 Kevin Hilman
2014-05-22 20:19 ` 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=7hd2f5icat.fsf@paris.lan \
--to=khilman@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.