From: Keith Packard <keithp@keithp.com>
To: Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk
Cc: Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Kees Cook <keescook@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 0/9] ARM: add support for IRQ stacks
Date: Mon, 11 Oct 2021 16:29:39 -0700 [thread overview]
Message-ID: <87tuhnxhr0.fsf@keithp.com> (raw)
In-Reply-To: <20211005071542.3127341-1-ardb@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
Ard Biesheuvel <ardb@kernel.org> writes:
> Ard Biesheuvel (9):
> ARM: remove some dead code
> ARM: assembler: introduce bl_r and bl_m macros
> ARM: optimize indirect call to handle_arch_irq for v7 cores
> ARM: unwind: support unwinding across multiple stacks
> ARM: export dump_mem() to other objects
> ARM: unwind: dump exception stack from calling frame
> ARM: implement IRQ stacks
> ARM: call_with_stack: add unwind support
> ARM: run softirqs on the per-CPU IRQ stack
I've been testing these patches on a Raspberry PI 2B (quad v7), doing
kernel builds and other modest workloads.
Tested-by: Keith Packard <keithpac@amazon.com>
--
-keith
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-11 23:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 7:15 [PATCH v2 0/9] ARM: add support for IRQ stacks Ard Biesheuvel
2021-10-05 7:15 ` [PATCH v2 1/9] ARM: remove some dead code Ard Biesheuvel
2021-10-05 12:06 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 2/9] ARM: assembler: introduce bl_r and bl_m macros Ard Biesheuvel
2021-10-05 12:10 ` Arnd Bergmann
2021-10-05 12:14 ` Ard Biesheuvel
2021-10-05 7:15 ` [PATCH v2 3/9] ARM: optimize indirect call to handle_arch_irq for v7 cores Ard Biesheuvel
2021-10-05 12:11 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 4/9] ARM: unwind: support unwinding across multiple stacks Ard Biesheuvel
2021-10-05 12:17 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 5/9] ARM: export dump_mem() to other objects Ard Biesheuvel
2021-10-05 12:15 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 6/9] ARM: unwind: dump exception stack from calling frame Ard Biesheuvel
2021-10-05 12:20 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 7/9] ARM: implement IRQ stacks Ard Biesheuvel
2021-10-05 12:26 ` Arnd Bergmann
2021-10-05 7:15 ` [PATCH v2 8/9] ARM: call_with_stack: add unwind support Ard Biesheuvel
2021-10-05 12:22 ` Arnd Bergmann
2021-10-05 18:46 ` Nick Desaulniers
2021-10-05 18:57 ` Ard Biesheuvel
2021-10-05 7:15 ` [PATCH v2 9/9] ARM: run softirqs on the per-CPU IRQ stack Ard Biesheuvel
2021-10-05 12:23 ` Arnd Bergmann
2021-10-06 15:21 ` Ard Biesheuvel
2021-10-11 23:29 ` Keith Packard [this message]
2021-10-16 22:04 ` [PATCH v2 0/9] ARM: add support for IRQ stacks Linus Walleij
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=87tuhnxhr0.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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).