linux-kernel.vger.kernel.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 for 5.15-rc1
Date: Fri, 10 Sep 2021 18:34:41 +0100	[thread overview]
Message-ID: <YTuXMRtjCu51AUj3@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below. Thanks.

The following changes since commit 65266a7c6abfa1ad915a362c41bf38576607f1f9:

  Merge remote-tracking branch 'tip/sched/arm64' into for-next/core (2021-08-31 09:10:00 +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 85f58eb1889826b9745737718723a80b639e0fbd:

  arm64: kdump: Skip kmemleak scan reserved memory for kdump (2021-09-10 11:58:59 +0100)

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

- Limit the linear region to 51-bit when KVM is running in nVHE mode
  otherwise, depending on the placement of the ID map, kernel-VA to
  hyp-VA translations may produce addresses that either conflict with
  other HYP mappings or generate addresses outside of the 52-bit
  addressable range.

- Instruct kmemleak not to scan the memory reserved for kdump as this
  range is removed from the kernel linear map and therefore not
  accessible.

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64: mm: limit linear region to 51 bits for KVM in nVHE mode

Chen Wandun (1):
      arm64: kdump: Skip kmemleak scan reserved memory for kdump

 arch/arm64/mm/init.c | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

-- 
Catalin

             reply	other threads:[~2021-09-10 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 17:34 Catalin Marinas [this message]
2021-09-10 19:26 ` [GIT PULL] arm64 fixes for 5.15-rc1 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=YTuXMRtjCu51AUj3@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).