From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/3] arm64: entry: Remove unnecessary calculation for S_SP in EL1h
Date: Mon, 07 Sep 2015 15:48:49 +0100 [thread overview]
Message-ID: <55EDA3D1.6020902@arm.com> (raw)
In-Reply-To: <1441376587-12979-2-git-send-email-jungseoklee85@gmail.com>
On 04/09/15 15:23, Jungseok Lee wrote:
> Under EL1h, S_SP data is not seen in kernel_exit. Thus, x21 calculation
> is not needed in kernel_entry. Currently, S_SP information is vaild only
> when sp_el0 is used.
>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index e163518..d23ca0d 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
> @@ -91,8 +91,6 @@
> get_thread_info tsk // Ensure MDSCR_EL1.SS is clear,
> ldr x19, [tsk, #TI_FLAGS] // since we can unmask debug
> disable_step_tsk x19, x20 // exceptions when scheduling.
> - .else
> - add x21, sp, #S_FRAME_SIZE
> .endif
> mrs x22, elr_el1
> mrs x23, spsr_el1
>
This sp value gets written to the struct pt_regs that is built on the
stack, and passed to the fault handlers, see 'el1_sp_pc' in kernel/entry.S,
which goes on to call do_sp_pc_abort() which prints this value out. (Other
fault handlers may make decisions based on this value).
It should be present and correct.
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com>
To: Jungseok Lee <jungseoklee85@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] arm64: entry: Remove unnecessary calculation for S_SP in EL1h
Date: Mon, 07 Sep 2015 15:48:49 +0100 [thread overview]
Message-ID: <55EDA3D1.6020902@arm.com> (raw)
In-Reply-To: <1441376587-12979-2-git-send-email-jungseoklee85@gmail.com>
On 04/09/15 15:23, Jungseok Lee wrote:
> Under EL1h, S_SP data is not seen in kernel_exit. Thus, x21 calculation
> is not needed in kernel_entry. Currently, S_SP information is vaild only
> when sp_el0 is used.
>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index e163518..d23ca0d 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
> @@ -91,8 +91,6 @@
> get_thread_info tsk // Ensure MDSCR_EL1.SS is clear,
> ldr x19, [tsk, #TI_FLAGS] // since we can unmask debug
> disable_step_tsk x19, x20 // exceptions when scheduling.
> - .else
> - add x21, sp, #S_FRAME_SIZE
> .endif
> mrs x22, elr_el1
> mrs x23, spsr_el1
>
This sp value gets written to the struct pt_regs that is built on the
stack, and passed to the fault handlers, see 'el1_sp_pc' in kernel/entry.S,
which goes on to call do_sp_pc_abort() which prints this value out. (Other
fault handlers may make decisions based on this value).
It should be present and correct.
Thanks,
James
next prev parent reply other threads:[~2015-09-07 14:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 14:23 [RFC PATCH 0/3] Implement IRQ stack on ARM64 Jungseok Lee
2015-09-04 14:23 ` Jungseok Lee
2015-09-04 14:23 ` [RFC PATCH 1/3] arm64: entry: Remove unnecessary calculation for S_SP in EL1h Jungseok Lee
2015-09-04 14:23 ` Jungseok Lee
2015-09-07 14:48 ` James Morse [this message]
2015-09-07 14:48 ` James Morse
2015-09-07 14:56 ` Mark Rutland
2015-09-07 14:56 ` Mark Rutland
2015-09-07 15:51 ` Jungseok Lee
2015-09-07 15:51 ` Jungseok Lee
2015-09-04 14:23 ` [RFC PATCH 2/3] arm64: Introduce IRQ stack Jungseok Lee
2015-09-04 14:23 ` Jungseok Lee
2015-09-04 17:12 ` Alexnader Kuleshov
2015-09-04 17:12 ` Alexnader Kuleshov
2015-09-07 14:08 ` Jungseok Lee
2015-09-07 14:08 ` Jungseok Lee
2015-09-07 14:48 ` James Morse
2015-09-07 14:48 ` James Morse
2015-09-08 14:28 ` Jungseok Lee
2015-09-08 14:28 ` Jungseok Lee
2015-09-04 14:23 ` [RFC PATCH 3/3] arm64: Reduce kernel stack size when using " Jungseok Lee
2015-09-04 14:23 ` Jungseok Lee
2015-09-07 14:33 ` [RFC PATCH 0/3] Implement IRQ stack on ARM64 James Morse
2015-09-07 14:33 ` James Morse
2015-09-07 14:36 ` [PATCH] arm64: kernel: Use a separate stack for irq interrupts James Morse
2015-09-07 14:36 ` James Morse
2015-09-07 15:48 ` Jungseok Lee
2015-09-07 15:48 ` Jungseok Lee
2015-09-07 16:06 ` James Morse
2015-09-07 16:06 ` James Morse
2015-09-07 16:34 ` Jungseok Lee
2015-09-07 16:34 ` Jungseok Lee
2015-09-08 1:45 ` AKASHI Takahiro
2015-09-08 1:45 ` AKASHI Takahiro
2015-09-08 6:44 ` AKASHI Takahiro
2015-09-08 6:44 ` AKASHI Takahiro
2015-09-08 14:59 ` Jungseok Lee
2015-09-08 14:59 ` Jungseok Lee
2015-09-08 7:51 ` AKASHI Takahiro
2015-09-08 7:51 ` AKASHI Takahiro
2015-09-08 14:54 ` Jungseok Lee
2015-09-08 14:54 ` Jungseok Lee
2015-09-08 16:47 ` James Morse
2015-09-08 16:47 ` James Morse
2015-09-09 13:22 ` Jungseok Lee
2015-09-09 13:22 ` Jungseok Lee
2015-09-09 18:13 ` James Morse
2015-09-09 18:13 ` James Morse
2015-09-10 23:30 ` Jungseok Lee
2015-09-10 23:30 ` Jungseok Lee
2015-09-07 15:42 ` [RFC PATCH 0/3] Implement IRQ stack on ARM64 Jungseok Lee
2015-09-07 15:42 ` Jungseok Lee
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=55EDA3D1.6020902@arm.com \
--to=james.morse@arm.com \
--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.