From: Maninder Singh <maninder1.s@samsung.com>
To: linux@armlinux.org.uk, ndesaulniers@google.com,
caij2003@gmail.com, tglx@linutronix.de, bigeasy@linutronix.de,
maz@kernel.org, valentin.schneider@arm.com,
vincent.whitchurch@axis.com, nhuck@google.com,
akpm@linux-foundation.org, 0x7f454c46@gmail.com, will@kernel.org
Cc: v.narang@samsung.com, Maninder Singh <maninder1.s@samsung.com>,
a.sahrawat@samsung.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] IRQ stack support for ARM
Date: Thu, 8 Oct 2020 12:45:30 +0530 [thread overview]
Message-ID: <1602141333-17822-1-git-send-email-maninder1.s@samsung.com> (raw)
In-Reply-To: CGME20201008071628epcas5p24d196a6023a47a3b0bfa7b7f231ec811@epcas5p2.samsung.com
Observed Stack Overflow on 8KB kernel stack on ARM specially
incase on network interrupts, which results in undeterministic behaviour.
So there is need for per cpu dedicated IRQ stack for ARM.
As ARm does not have extra co-processor register
to save thread info pointer, IRQ stack will be at some
performance cost, so code is under CONFIG_IRQ_STACK.
and we don't have much knowledge and set up for CLANG
and ARM_UNWIND, so dependency added for both cases.
Tested patch set with QEMU for latest kernel
and 4.1 kernel for ARM target with same patch set.
Maninder Singh, Vaneet Narang (3):
arm: introduce self pointer in thread info
arm: introduce IRQ stacks
arm: Modify stack trace and dump for use with irq stack
arch/arm/Kconfig | 10 ++++++++
arch/arm/include/asm/assembler.h | 11 +++++++++
arch/arm/include/asm/irq.h | 13 +++++++++++
arch/arm/include/asm/thread_info.h | 27 ++++++++++++++++++++++
arch/arm/kernel/entry-armv.S | 41 ++++++++++++++++++++++++++++++++-
arch/arm/kernel/irq.c | 24 +++++++++++++++++++
arch/arm/kernel/stacktrace.c | 21 +++++++++++++++++
arch/arm/kernel/traps.c | 47 +++++++++++++++++++++++++++++++++++---
arch/arm/lib/backtrace.S | 18 +++++++++++++++
include/linux/thread_info.h | 4 ++++
kernel/fork.c | 1 +
11 files changed, 213 insertions(+), 4 deletions(-)
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2020-10-08 7:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201008071628epcas5p24d196a6023a47a3b0bfa7b7f231ec811@epcas5p2.samsung.com>
2020-10-08 7:15 ` Maninder Singh [this message]
[not found] ` <CGME20201008071633epcas5p20f5c533ac67ab235997e7e4a8ad3022b@epcas5p2.samsung.com>
2020-10-08 7:15 ` [PATCH 1/3] arm: introduce self pointer in thread info Maninder Singh
[not found] ` <CGME20201008071639epcas5p465f13d992a25936ba63436baf1fb6f83@epcas5p4.samsung.com>
2020-10-08 7:15 ` [PATCH 2/3] arm: introduce IRQ stacks Maninder Singh
[not found] ` <CAK8P3a2RYeNiTy9QmwFVKtFifXxWc9XfAT6ThPoSH9wGYsKGpA@mail.gmail.com>
2020-10-21 12:42 ` Arnd Bergmann
2020-10-21 12:45 ` Russell King - ARM Linux admin
2020-10-21 12:55 ` Arnd Bergmann
2020-10-21 12:57 ` Russell King - ARM Linux admin
2020-10-21 15:59 ` Arnd Bergmann
2020-11-09 14:45 ` Tony Lindgren
2020-11-09 19:10 ` Arnd Bergmann
2020-11-10 9:19 ` Tony Lindgren
2020-11-10 10:04 ` Arnd Bergmann
2020-11-10 12:04 ` Tony Lindgren
2020-11-10 13:35 ` Arnd Bergmann
2020-11-11 6:56 ` Tony Lindgren
[not found] ` <CGME20201008071639epcas5p465f13d992a25936ba63436baf1fb6f83@epcms5p7>
2020-10-21 13:46 ` Vaneet Narang
[not found] ` <CGME20201008071644epcas5p1f5c220b5f58fd4251695af147325b7c4@epcas5p1.samsung.com>
2020-10-08 7:15 ` [PATCH 3/3] arm: Modify stack trace and dump for use with irq stack Maninder Singh
2020-10-08 7:53 ` [PATCH 0/3] IRQ stack support for ARM Sebastian Andrzej Siewior
2020-10-08 8:30 ` Russell King - ARM Linux admin
2020-10-15 20:59 ` Nick Desaulniers
2020-10-15 21:16 ` Florian Fainelli
[not found] ` <CAK8P3a0h=D8_Kn_fpHbsik_jf4to2jayxj7K7B7=HaNFzKqNnw@mail.gmail.com>
2020-10-21 11:58 ` Arnd Bergmann
2020-10-21 12:34 ` Russell King - ARM Linux admin
2020-10-21 12:46 ` Arnd Bergmann
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=1602141333-17822-1-git-send-email-maninder1.s@samsung.com \
--to=maninder1.s@samsung.com \
--cc=0x7f454c46@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=caij2003@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nhuck@google.com \
--cc=tglx@linutronix.de \
--cc=v.narang@samsung.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.whitchurch@axis.com \
--cc=will@kernel.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).