All of lore.kernel.org
 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>, James Morse <james.morse@arm.com>,
	Ben Horgan <ben.horgan@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 7.1-rc4
Date: Fri, 15 May 2026 18:45:01 +0100	[thread overview]
Message-ID: <agdbnfcTQATqM1K8@arm.com> (raw)

Hi Linus,

Please pull the MPAM fixes below. Thanks.

The following changes since commit 5cbb61bf4168859d97c068d88d364f4f1f440325:

  arm64/fpsimd: ptrace: zero target's fpsimd_state, not the tracer's (2026-05-06 12:11:49 +0100)

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 6ccbb613b42a1f1ba7bfd547a148f644a902a25c:

  arm_mpam: Check whether the config array is allocated before destroying it (2026-05-14 09:52:05 +0100)

----------------------------------------------------------------
arm64 MPAM fixes:

 - Fix NULL dereference and a false-positive warning when the driver
   probes hardware with surprising version numbers

 - Fix writing values to the wrong registers when probing
   cache-utilisation counters. Replace 'NRDY' probing with a version
   that is robust for platforms where the bit is writeable by both
   hardware and software

----------------------------------------------------------------
Ben Horgan (3):
      arm_mpam: Fix monitor instance selection when checking for hardware NRDY
      arm_mpam: Pretend that NRDY is always hardware managed
      arm_mpam: Improve check for whether or not NRDY is hardware managed

James Morse (2):
      arm_mpam: Fix false positive assert failure during mpam_disable()
      arm_mpam: Check whether the config array is allocated before destroying it

 drivers/resctrl/mpam_devices.c  | 81 ++++++++++++++++++++---------------------
 drivers/resctrl/mpam_internal.h |  2 -
 2 files changed, 40 insertions(+), 43 deletions(-)

-- 
Catalin

             reply	other threads:[~2026-05-15 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 17:45 Catalin Marinas [this message]
2026-05-16  0:06 ` [GIT PULL] arm64 fixes for 7.1-rc4 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=agdbnfcTQATqM1K8@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=ben.horgan@arm.com \
    --cc=james.morse@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 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.