From: Ard Biesheuvel <ardb@kernel.org>
To: linux+pull@armlinux.org.uk
Cc: linux-arm-kernel@lists.infradead.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] IRQ and vmap'ed stacks roundup for v5.18
Date: Mon, 31 Jan 2022 16:12:35 +0100 [thread overview]
Message-ID: <20220131151235.92759-1-ardb@kernel.org> (raw)
Hello Russell,
As discussed on IRC last week, here is the pull request containing the fixes
and minor adjustments for the IRQ and vmap'ed stacks code that is already
queued up in your devel-stable branch.
Thanks,
Ard.
The following changes since commit 5fe41793bc78d9bb47fea37d1a16984ad6cf294b:
ARM: 9176/1: avoid literal references in inline assembly (2022-01-06 12:58:58 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git tags/arm-vmap-stacks-v6
for you to fetch changes up to 4d5a643e738c6b6ccc1a05f6938643c3f08df29b:
ARM: make get_current() and __my_cpu_offset() __always_inline (2022-01-31 16:06:35 +0100)
----------------------------------------------------------------
ARM: support for IRQ and vmap'ed stacks [v6]
This tag covers the changes between the version of vmap'ed + IRQ stacks
support pulled into rmk/devel-stable [0] (which was dropped from v5.17
due to issues discovered too late in the cycle), and my v5 proposed for
the v5.18 cycle [1].
[0] git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git arm-irq-and-vmap-stacks-for-rmk
[1] https://lore.kernel.org/linux-arm-kernel/20220124174744.1054712-1-ardb@kernel.org/
----------------------------------------------------------------
Ard Biesheuvel (8):
ARM: mm: switch to swapper_pg_dir early for vmap'ed stack
ARM: assembler: define a Kconfig symbol for group relocation support
ARM: smp: elide HWCAP_TLS checks or __entry_task updates on SMP+v6
ARM: entry: avoid clobbering R9 in IRQ handler
ARM: mm: make vmalloc_seq handling SMP safe
ARM: iop: make iop_handle_irq() static
ARM: drop pointless SMP check on secondary startup path
ARM: make get_current() and __my_cpu_offset() __always_inline
arch/arm/Kconfig | 13 ++++++++++++-
arch/arm/include/asm/assembler.h | 8 ++++----
arch/arm/include/asm/current.h | 10 +++++-----
arch/arm/include/asm/mmu.h | 2 +-
arch/arm/include/asm/mmu_context.h | 22 ++++++++++++++++++++--
arch/arm/include/asm/page.h | 3 +--
arch/arm/include/asm/percpu.h | 6 +++---
arch/arm/include/asm/switch_to.h | 4 ++--
arch/arm/include/asm/tls.h | 22 ++++++++++++++++------
arch/arm/kernel/entry-armv.S | 9 ++++-----
arch/arm/kernel/entry-header.S | 17 +++++++----------
arch/arm/kernel/head.S | 7 +++++++
arch/arm/kernel/module.c | 7 ++++++-
arch/arm/kernel/sleep.S | 7 +++++++
arch/arm/kernel/smp.c | 5 -----
arch/arm/kernel/traps.c | 25 +++++++------------------
arch/arm/mach-iop32x/irq.c | 2 +-
arch/arm/mm/context.c | 3 +--
arch/arm/mm/ioremap.c | 18 +++++++++++-------
19 files changed, 115 insertions(+), 75 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-01-31 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220131151235.92759-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=linux+pull@armlinux.org.uk \
--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).