From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/18] KVM: arm64: nv: Support for EL2 PMU controls
Date: Wed, 30 Oct 2024 08:45:48 +0000 [thread overview]
Message-ID: <87h68ut1vn.wl-maz@kernel.org> (raw)
In-Reply-To: <20241025182354.3364124-1-oliver.upton@linux.dev>
On Fri, 25 Oct 2024 19:23:35 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> v3 -> v4:
> - Align sysreg definitions with DDI0601 2024-09
> - Fix 'accessible' counter mask construction
> - Fix MDCR_EL2.MTPME RES0 logic
>
> v3: https://lore.kernel.org/kvmarm/20241007174559.1830205-1-oliver.upton@linux.dev/
>
> Marc Zyngier (1):
> KVM: arm64: Extend masking facility to arbitrary registers
>
> Oliver Upton (17):
> arm64: sysreg: Describe ID_AA64DFR2_EL1 fields
> arm64: sysreg: Migrate MDCR_EL2 definition to table
> arm64: sysreg: Add new definitions for ID_AA64DFR0_EL1
> KVM: arm64: Describe RES0/RES1 bits of MDCR_EL2
> KVM: arm64: nv: Allow coarse-grained trap combos to use complex traps
> KVM: arm64: nv: Rename BEHAVE_FORWARD_ANY
> KVM: arm64: nv: Reinject traps that take effect in Host EL0
> KVM: arm64: nv: Honor MDCR_EL2.{TPM, TPMCR} in Host EL0
> KVM: arm64: nv: Describe trap behaviour of MDCR_EL2.HPMN
> KVM: arm64: nv: Advertise support for FEAT_HPMN0
> KVM: arm64: Rename kvm_pmu_valid_counter_mask()
> KVM: arm64: nv: Adjust range of accessible PMCs according to HPMN
> KVM: arm64: Add helpers to determine if PMC counts at a given EL
> KVM: arm64: nv: Honor MDCR_EL2.HPME
> KVM: arm64: nv: Honor MDCR_EL2.HLP
> KVM: arm64: nv: Apply EL2 event filtering when in hyp context
> KVM: arm64: nv: Reprogram PMU events affected by nested transition
>
> arch/arm64/include/asm/kvm_arm.h | 29 ---
> arch/arm64/include/asm/kvm_emulate.h | 5 +
> arch/arm64/include/asm/kvm_host.h | 21 +-
> arch/arm64/kvm/emulate-nested.c | 291 ++++++++++++++++-----------
> arch/arm64/kvm/nested.c | 54 ++++-
> arch/arm64/kvm/pmu-emul.c | 143 +++++++++++--
> arch/arm64/kvm/sys_regs.c | 15 +-
> arch/arm64/tools/sysreg | 76 ++++++-
> include/kvm/arm_pmu.h | 18 +-
> 9 files changed, 465 insertions(+), 187 deletions(-)
>
>
> base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354
I think this is pretty much good to go, and with the couple of nits
mentioned before fixed:
Reviewed-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-10-30 8:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 18:23 [PATCH v4 00/18] KVM: arm64: nv: Support for EL2 PMU controls Oliver Upton
2024-10-25 18:23 ` [PATCH v4 01/18] KVM: arm64: Extend masking facility to arbitrary registers Oliver Upton
2024-10-25 18:23 ` [PATCH v4 02/18] arm64: sysreg: Describe ID_AA64DFR2_EL1 fields Oliver Upton
2024-10-25 18:23 ` [PATCH v4 03/18] arm64: sysreg: Migrate MDCR_EL2 definition to table Oliver Upton
2024-10-25 18:23 ` [PATCH v4 04/18] arm64: sysreg: Add new definitions for ID_AA64DFR0_EL1 Oliver Upton
2024-10-25 18:23 ` [PATCH v4 05/18] KVM: arm64: Describe RES0/RES1 bits of MDCR_EL2 Oliver Upton
2024-10-25 18:23 ` [PATCH v4 06/18] KVM: arm64: nv: Allow coarse-grained trap combos to use complex traps Oliver Upton
2024-10-25 18:23 ` [PATCH v4 07/18] KVM: arm64: nv: Rename BEHAVE_FORWARD_ANY Oliver Upton
2024-10-25 18:23 ` [PATCH v4 08/18] KVM: arm64: nv: Reinject traps that take effect in Host EL0 Oliver Upton
2024-10-26 8:13 ` Marc Zyngier
2024-10-26 14:35 ` Oliver Upton
2024-10-29 9:45 ` Anshuman Khandual
2024-10-25 18:23 ` [PATCH v4 09/18] KVM: arm64: nv: Honor MDCR_EL2.{TPM, TPMCR} " Oliver Upton
2024-10-25 18:23 ` [PATCH v4 10/18] KVM: arm64: nv: Describe trap behaviour of MDCR_EL2.HPMN Oliver Upton
2024-10-26 10:21 ` kernel test robot
2024-10-26 10:42 ` kernel test robot
2024-10-26 14:32 ` Oliver Upton
2024-10-25 18:23 ` [PATCH v4 11/18] KVM: arm64: nv: Advertise support for FEAT_HPMN0 Oliver Upton
2024-10-25 18:23 ` [PATCH v4 12/18] KVM: arm64: Rename kvm_pmu_valid_counter_mask() Oliver Upton
2024-10-25 18:23 ` [PATCH v4 13/18] KVM: arm64: nv: Adjust range of accessible PMCs according to HPMN Oliver Upton
2024-10-25 18:23 ` [PATCH v4 14/18] KVM: arm64: Add helpers to determine if PMC counts at a given EL Oliver Upton
2024-10-25 18:23 ` [PATCH v4 15/18] KVM: arm64: nv: Honor MDCR_EL2.HPME Oliver Upton
2024-10-25 18:23 ` [PATCH v4 16/18] KVM: arm64: nv: Honor MDCR_EL2.HLP Oliver Upton
2024-10-25 18:23 ` [PATCH v4 17/18] KVM: arm64: nv: Apply EL2 event filtering when in hyp context Oliver Upton
2024-10-25 18:25 ` [PATCH v4 18/18] KVM: arm64: nv: Reprogram PMU events affected by nested transition Oliver Upton
2024-10-30 8:45 ` Marc Zyngier [this message]
2024-10-31 19:34 ` [PATCH v4 00/18] KVM: arm64: nv: Support for EL2 PMU controls Oliver Upton
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=87h68ut1vn.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@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=oliver.upton@linux.dev \
--cc=suzuki.poulose@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;
as well as URLs for NNTP newsgroup(s).