linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes/updates for 5.13-rc2
Date: Fri, 14 May 2021 18:29:06 +0100	[thread overview]
Message-ID: <20210514172904.GA29470@arm.com> (raw)

Hi Linus,

Please pull the arm64 updates below. Thanks.

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes

for you to fetch changes up to 588a513d34257fdde95a9f0df0202e31998e85c6:

  arm64: Fix race condition on PG_dcache_clean in __sync_icache_dcache() (2021-05-14 17:11:16 +0100)

----------------------------------------------------------------
arm64 fixes and cpucaps.h automatic generation:

- Generate cpucaps.h at build time rather than carrying lots of
  #defines. Merged at -rc1 to avoid some conflicts during the merging
  window.

- Initialise RGSR_EL1.SEED in __cpu_setup() as it may be left as 0 out
  of reset and the IRG instruction would not function as expected if
  only the architected pseudorandom number generator is implemented.

- Fix potential race condition in __sync_icache_dcache() where the
  PG_dcache_clean page flag is set before the actual cache maintenance.

- Fix header include in BTI kselftests.

----------------------------------------------------------------
Catalin Marinas (1):
      arm64: Fix race condition on PG_dcache_clean in __sync_icache_dcache()

Mark Brown (3):
      arm64: Generate cpucaps.h
      kselftest/arm64: Add missing stddef.h include to BTI tests
      arm64: tools: Add __ASM_CPUCAPS_H to the endif in cpucaps.h

Peter Collingbourne (1):
      arm64: mte: initialize RGSR_EL1.SEED in __cpu_setup

 arch/arm64/Makefile                      |  3 ++
 arch/arm64/include/asm/Kbuild            |  2 +
 arch/arm64/include/asm/cpucaps.h         | 74 --------------------------------
 arch/arm64/mm/flush.c                    |  4 +-
 arch/arm64/mm/proc.S                     | 12 ++++++
 arch/arm64/tools/Makefile                | 22 ++++++++++
 arch/arm64/tools/cpucaps                 | 65 ++++++++++++++++++++++++++++
 arch/arm64/tools/gen-cpucaps.awk         | 40 +++++++++++++++++
 tools/testing/selftests/arm64/bti/test.c |  1 +
 9 files changed, 148 insertions(+), 75 deletions(-)
 delete mode 100644 arch/arm64/include/asm/cpucaps.h
 create mode 100644 arch/arm64/tools/Makefile
 create mode 100644 arch/arm64/tools/cpucaps
 create mode 100755 arch/arm64/tools/gen-cpucaps.awk

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-05-14 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 17:29 Catalin Marinas [this message]
2021-05-14 18:00 ` [GIT PULL] arm64 fixes/updates for 5.13-rc2 pr-tracker-bot

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=20210514172904.GA29470@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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).