From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, Oliver Upton <oliver.upton@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Raghavendra Rao Ananta <rananta@google.com>
Subject: Re: (subset) [PATCH 0/2] KVM: arm64: Revert resched fixes for stage-2 destruction
Date: Wed, 10 Sep 2025 11:12:16 -0700 [thread overview]
Message-ID: <175752793035.3680647.2017483654702951958.b4-ty@linux.dev> (raw)
In-Reply-To: <20250910180930.3679473-1-oliver.upton@linux.dev>
On Wed, 10 Sep 2025 11:09:27 -0700, Oliver Upton wrote:
> We're getting pretty late in the cycle and things haven't settled down
> yet on the resched fixes. At this point a revert seems like the best
> idea so we can let an improved version bake a bit longer.
>
> Oliver Upton (2):
> Revert "KVM: arm64: Reschedule as needed when destroying the stage-2
> page-tables"
> Revert "KVM: arm64: Split kvm_pgtable_stage2_destroy()"
>
> [...]
Applied to fixes, thanks!
[1/2] Revert "KVM: arm64: Reschedule as needed when destroying the stage-2 page-tables"
https://git.kernel.org/kvmarm/kvmarm/c/fc670ad5966f
[2/2] Revert "KVM: arm64: Split kvm_pgtable_stage2_destroy()"
https://git.kernel.org/kvmarm/kvmarm/c/e6157256ee1a
--
Best,
Oliver
prev parent reply other threads:[~2025-09-10 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 18:09 [PATCH 0/2] KVM: arm64: Revert resched fixes for stage-2 destruction Oliver Upton
2025-09-10 18:09 ` [PATCH 1/2] Revert "KVM: arm64: Reschedule as needed when destroying the stage-2 page-tables" Oliver Upton
2025-09-10 18:09 ` [PATCH 2/2] Revert "KVM: arm64: Split kvm_pgtable_stage2_destroy()" Oliver Upton
2025-09-10 18:09 ` [PATCH] bad bad bad Oliver Upton
2025-09-10 18:12 ` 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=175752793035.3680647.2017483654702951958.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
--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