From: Oliver Upton <oupton@kernel.org>
To: Marc Zyngier <maz@kernel.org>, Fuad Tabba <fuad.tabba@linux.dev>
Cc: Oliver Upton <oupton@kernel.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Vincent Donnefort <vdonnefort@google.com>,
Wei-Lin Chang <weilin.chang@arm.com>
Subject: Re: [PATCH v3 0/2] KVM: arm64: Stop stage-2 teardown scaling with the IPA size
Date: Tue, 17 Nov 2026 13:57:23 -0800 [thread overview]
Message-ID: <179495264130.1456871.12453105511491068179.b4-ty@kernel.org> (raw)
In-Reply-To: <20261106133000.453240-1-fuad.tabba@linux.dev>
On Fri, 06 Nov 2026 13:29:58 +0000, Fuad Tabba wrote:
> Changes since v2 [1]:
> - Return a failed walk's error to the callers and warn there, instead
> of inside the walk. (Oliver)
> - Dropped the comment on the next-mapping lookup. (Vincent)
> - Collected Reviewed-by from Vincent on patch 2. (thanks!)
>
> Two patches that make stage-2 teardown take time proportional to what
> is mapped, rather than to the size of the IPA space as it has since
> 4ddfab5436b6.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Resume stage-2 teardown where the walk stopped
https://git.kernel.org/kvmarm/kvmarm/c/6607becfb034
[2/2] KVM: arm64: Resume a pKVM stage-2 teardown at the next mapping
https://git.kernel.org/kvmarm/kvmarm/c/737a5ff38ccd
--
Best,
Oliver
prev parent reply other threads:[~2026-11-17 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:29 Fuad Tabba
2026-11-06 13:29 ` [PATCH v3 1/2] KVM: arm64: Resume stage-2 teardown where the walk stopped Fuad Tabba
2026-11-06 13:30 ` [PATCH v3 2/2] KVM: arm64: Resume a pKVM stage-2 teardown at the next mapping Fuad Tabba
2026-11-17 21:57 ` Oliver Upton [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=179495264130.1456871.12453105511491068179.b4-ty@kernel.org \
--to=oupton@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--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=maz@kernel.org \
--cc=rananta@google.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®