From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, Dev Jain <dev.jain@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
anshuman.khandual@arm.com, quic_zhenhuah@quicinc.com,
ryan.roberts@arm.com, kevin.brodsky@arm.com,
yangyicong@hisilicon.com, joey.gouly@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, david@redhat.com,
mark.rutland@arm.com, urezki@gmail.com, jthoughton@google.com
Subject: Re: [PATCH v6] arm64: Enable vmalloc-huge with ptdump
Date: Mon, 22 Sep 2025 14:14:46 +0100 [thread overview]
Message-ID: <175853832495.3123711.10100627692023962115.b4-ty@kernel.org> (raw)
In-Reply-To: <20250922064126.63016-1-dev.jain@arm.com>
On Mon, 22 Sep 2025 12:11:26 +0530, Dev Jain wrote:
> Our goal is to move towards enabling vmalloc-huge by default on arm64 so
> as to reduce TLB pressure. Therefore, we need a way to analyze the portion
> of block mappings in vmalloc space we can get on a production system; this
> can be done through ptdump, but currently we disable vmalloc-huge if
> CONFIG_PTDUMP_DEBUGFS is on. The reason is that lazy freeing of kernel
> pagetables via vmap_try_huge_pxd() may race with ptdump, so ptdump
> may dereference a bogus address.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: Enable vmalloc-huge with ptdump
https://git.kernel.org/arm64/c/fa93b45fd397
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-09-22 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 6:41 Dev Jain
2025-09-22 13:14 ` Will Deacon [this message]
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=175853832495.3123711.10100627692023962115.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=joey.gouly@arm.com \
--cc=jthoughton@google.com \
--cc=kernel-team@android.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=ryan.roberts@arm.com \
--cc=urezki@gmail.com \
--cc=yangyicong@hisilicon.com \
/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
all inboxes | Powered by JetHome®