[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175092438911.7995.9528618735352034955.b4-ty@kernel.org>
Date: Thu, 26 Jun 2025 08:53:15 +0100
From: Marc Zyngier <maz@...nel.org>
To: Oliver Upton <oliver.upton@...ux.dev>,
Joey Gouly <joey.gouly@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Quentin Perret <qperret@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: arm64: Adjust range correctly during host stage-2 faults
On Wed, 25 Jun 2025 10:55:48 +0000, Quentin Perret wrote:
> host_stage2_adjust_range() tries to find the largest block mapping that
> fits within a memory or mmio region (represented by a kvm_mem_range in
> this function) during host stage-2 faults under pKVM. To do so, it walks
> the host stage-2 page-table, finds the faulting PTE and its level, and
> then progressively increments the level until it finds a granule of the
> appropriate size. However, the condition in the loop implementing the
> above is broken as it checks kvm_level_supports_block_mapping() for the
> next level instead of the current, so pKVM may attempt to map a region
> larger than can be covered with a single block.
>
> [...]
Applied to fixes, thanks!
[1/1] KVM: arm64: Adjust range correctly during host stage-2 faults
commit: e728e705802fec20f65d974a5d5eb91217ac618d
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists