From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Marc Zyngier <maz@kernel.org>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v4 00/19] KVM: arm64: Debug cleanups
Date: Fri, 4 Apr 2025 09:55:12 -0700 [thread overview]
Message-ID: <Z_AO8A_GGHLg7FuH@linux.dev> (raw)
In-Reply-To: <20250404165233.3205127-11-oliver.upton@linux.dev>
Oops, forgot to clean out directory where I stage patches.
Thanks,
Oliver
On Fri, Apr 04, 2025 at 09:52:33AM -0700, Oliver Upton wrote:
> Hopefully the last round.
>
> v3 -> v4:
> - Collect Tested-by from James (thanks!)
> - Delete stray if condition (Marc)
> - Write mdcr_el2 from kvm_arm_setup_mdcr_el2() on VHE
> - Purge DBGxVR/DBGxCR accessors since it isn't nice to look at
>
> Oliver Upton (19):
> KVM: arm64: Drop MDSCR_EL1_DEBUG_MASK
> KVM: arm64: Get rid of __kvm_get_mdcr_el2() and related warts
> KVM: arm64: Track presence of SPE/TRBE in kvm_host_data instead of
> vCPU
> KVM: arm64: Move host SME/SVE tracking flags to host data
> KVM: arm64: Write MDCR_EL2 directly from kvm_arm_setup_mdcr_el2()
> KVM: arm64: Evaluate debug owner at vcpu_load()
> KVM: arm64: Clean up KVM_SET_GUEST_DEBUG handler
> KVM: arm64: Select debug state to save/restore based on debug owner
> KVM: arm64: Remove debug tracepoints
> KVM: arm64: Remove vestiges of debug_ptr
> KVM: arm64: Use debug_owner to track if debug regs need save/restore
> KVM: arm64: Reload vCPU for accesses to OSLAR_EL1
> KVM: arm64: Compute MDCR_EL2 at vcpu_load()
> KVM: arm64: Don't hijack guest context MDSCR_EL1
> KVM: arm64: Manage software step state at load/put
> KVM: arm64: nv: Honor MDCR_EL2.TDE routing for debug exceptions
> KVM: arm64: Avoid reading ID_AA64DFR0_EL1 for debug save/restore
> KVM: arm64: Fold DBGxVR/DBGxCR accessors into common set
> KVM: arm64: Promote guest ownership for DBGxVR/DBGxCR reads
>
> arch/arm64/include/asm/kvm_asm.h | 5 +-
> arch/arm64/include/asm/kvm_host.h | 94 ++---
> arch/arm64/include/asm/kvm_nested.h | 1 +
> arch/arm64/kvm/arm.c | 14 +-
> arch/arm64/kvm/debug.c | 384 +++++++--------------
> arch/arm64/kvm/emulate-nested.c | 23 +-
> arch/arm64/kvm/fpsimd.c | 12 +-
> arch/arm64/kvm/guest.c | 31 +-
> arch/arm64/kvm/handle_exit.c | 5 +-
> arch/arm64/kvm/hyp/include/hyp/debug-sr.h | 42 ++-
> arch/arm64/kvm/hyp/include/hyp/sysreg-sr.h | 43 ++-
> arch/arm64/kvm/hyp/nvhe/debug-sr.c | 13 +-
> arch/arm64/kvm/hyp/nvhe/hyp-main.c | 8 -
> arch/arm64/kvm/hyp/vhe/debug-sr.c | 5 -
> arch/arm64/kvm/sys_regs.c | 245 ++++---------
> arch/arm64/kvm/trace_handle_exit.h | 75 ----
> 16 files changed, 353 insertions(+), 647 deletions(-)
>
>
> base-commit: 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-04-04 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 16:52 [PATCH kvmtool v2 0/9] arm: Drop support for 32-bit kvmtool Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 1/9] Drop support for 32-bit arm Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 2/9] arm64: Move arm64-only features into main directory Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 3/9] arm64: Combine kvm.c Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 4/9] arm64: Merge kvm-cpu.c Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 5/9] arm64: Combine kvm-config-arch.h Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 6/9] arm64: Move remaining kvm/* headers Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 7/9] arm64: Move asm headers Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 8/9] arm64: Rename top-level directory Oliver Upton
2025-04-04 16:52 ` [PATCH kvmtool v2 9/9] arm64: Get rid of the 'arm-common' include directory Oliver Upton
2025-04-04 16:52 ` [PATCH v4 00/19] KVM: arm64: Debug cleanups Oliver Upton
2025-04-04 16:55 ` Oliver Upton [this message]
2025-04-17 14:27 ` [PATCH kvmtool v2 0/9] arm: Drop support for 32-bit kvmtool 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=Z_AO8A_GGHLg7FuH@linux.dev \
--to=oliver.upton@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=will@kernel.org \
/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