From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>, Wei-Lin Chang <weilin.chang@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Oliver Upton <oupton@kernel.org>, Fuad Tabba <tabba@google.com>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Dev Jain <dev.jain@arm.com>, Ard Biesheuvel <ardb@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Vincent Donnefort <vdonnefort@google.com>,
Sebastian Ene <sebastianene@google.com>
Subject: Re: [PATCH v3 0/2] arm64: ptdump flush fixes
Date: Sun, 23 Aug 2026 11:13:15 +0100 [thread overview]
Message-ID: <87h5klno04.wl-maz@kernel.org> (raw)
In-Reply-To: <20260814222458.584906-1-weilin.chang@arm.com>
On Fri, 14 Aug 2026 23:24:56 +0100,
Wei-Lin Chang <weilin.chang@arm.com> wrote:
>
> Hi,
>
> This series fixes two problems around ptdumps:
>
> 1. note_page_flush(), which flushes out the last row of ptdumps, does
> not account for address spaces that have IA < 64. Other than making
> the last region extremely huge, the attributes of the last region
> within the address spaces appear to extend all the way to 1 << 64.
>
> 2. KVM/arm64's stage-2 ptdump missed calling note_page_flush().
>
> To address Will's comment [1], I have created an end_address field for
> struct ptdump_pg_state, and initialized it with the end address of the
> ptdumps. It follows the same convention as the last range->end:
> exclusive end, except for the case where the address space ends at
> 1 << 64. In that case it is set as ULONG_MAX.
>
> Caching the end address avoids duplicating the range iteration in
> note_page_flush(), at the cost of duplicating state in ptdump_pg_state.
>
> Series is based on v7.2-rc5.
Reviewed-by: Marc Zyngier <maz@kernel.org>
Will, if you're OK with patch #1, do you want the whole thing to go
via the arm64 or the kvmarm tree?
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2026-08-23 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 22:24 [PATCH v3 0/2] arm64: ptdump flush fixes Wei-Lin Chang
2026-08-14 22:24 ` [PATCH v3 1/2] arm64: ptdump: Make note_page_flush() range aware Wei-Lin Chang
2026-08-15 11:28 ` Marc Zyngier
2026-08-15 23:16 ` Wei-Lin Chang
2026-08-14 22:24 ` [PATCH v3 2/2] KVM: arm64: ptdump: Flush the last region Wei-Lin Chang
2026-08-23 10:13 ` Marc Zyngier [this message]
2026-08-24 13:30 ` [PATCH v3 0/2] arm64: ptdump flush fixes Will Deacon
2026-08-24 16:01 ` Will Deacon
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=87h5klno04.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=oupton@kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=sebastianene@google.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vdonnefort@google.com \
--cc=weilin.chang@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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