From: Reiji Watanabe <reijiw@google.com>
To: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Ricardo Koller <ricarkol@google.com>,
Jing Zhang <jingzhangos@google.com>,
Raghavendra Rao Anata <rananta@google.com>,
Will Deacon <will@kernel.org>, Reiji Watanabe <reijiw@google.com>
Subject: [PATCH 0/2] KVM: arm64: PMU: Preserve vPMC registers properly on migration
Date: Wed, 1 Mar 2023 21:50:31 -0800 [thread overview]
Message-ID: <20230302055033.3081456-1-reijiw@google.com> (raw)
The series fixes two problems in preserving vPMU counter (vPMC)
registers (PMCCNTR_EL0/PMEVCNTR<n>_EL0) during migration.
One of the problems is that KVM may not return the current values
of the vPMC registers for KVM_GET_ONE_REG.
The other one might cause KVM to reset the vPMC registers on the
first KVM_RUN on the destination. This is because userspace might
save PMCR_EL0 with PMCR_EL0.{C,P} bits set on the source, and
restore it on the destination.
See patch-1 and patch-2 for details on these issues respectively.
The series is based on v6.2.
Reiji Watanabe (2):
KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current
value
KVM: arm64: PMU: Don't save PMCR_EL0.{C,P} for the vCPU
arch/arm64/kvm/pmu-emul.c | 4 +++-
arch/arm64/kvm/sys_regs.c | 21 +++++++++++++++++++--
2 files changed, 22 insertions(+), 3 deletions(-)
base-commit: c9c3395d5e3dcc6daee66c6908354d47bf98cb0c
--
2.39.2.722.g9855ee24e9-goog
WARNING: multiple messages have this Message-ID (diff)
From: Reiji Watanabe <reijiw@google.com>
To: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Ricardo Koller <ricarkol@google.com>,
Jing Zhang <jingzhangos@google.com>,
Raghavendra Rao Anata <rananta@google.com>,
Will Deacon <will@kernel.org>,
Reiji Watanabe <reijiw@google.com>
Subject: [PATCH 0/2] KVM: arm64: PMU: Preserve vPMC registers properly on migration
Date: Wed, 1 Mar 2023 21:50:31 -0800 [thread overview]
Message-ID: <20230302055033.3081456-1-reijiw@google.com> (raw)
The series fixes two problems in preserving vPMU counter (vPMC)
registers (PMCCNTR_EL0/PMEVCNTR<n>_EL0) during migration.
One of the problems is that KVM may not return the current values
of the vPMC registers for KVM_GET_ONE_REG.
The other one might cause KVM to reset the vPMC registers on the
first KVM_RUN on the destination. This is because userspace might
save PMCR_EL0 with PMCR_EL0.{C,P} bits set on the source, and
restore it on the destination.
See patch-1 and patch-2 for details on these issues respectively.
The series is based on v6.2.
Reiji Watanabe (2):
KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current
value
KVM: arm64: PMU: Don't save PMCR_EL0.{C,P} for the vCPU
arch/arm64/kvm/pmu-emul.c | 4 +++-
arch/arm64/kvm/sys_regs.c | 21 +++++++++++++++++++--
2 files changed, 22 insertions(+), 3 deletions(-)
base-commit: c9c3395d5e3dcc6daee66c6908354d47bf98cb0c
--
2.39.2.722.g9855ee24e9-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-03-02 5:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 5:50 Reiji Watanabe [this message]
2023-03-02 5:50 ` [PATCH 0/2] KVM: arm64: PMU: Preserve vPMC registers properly on migration Reiji Watanabe
2023-03-02 5:50 ` [PATCH 1/2] KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current value Reiji Watanabe
2023-03-02 5:50 ` Reiji Watanabe
2023-03-12 14:57 ` Marc Zyngier
2023-03-12 14:57 ` Marc Zyngier
2023-03-13 3:34 ` Reiji Watanabe
2023-03-13 3:34 ` Reiji Watanabe
2023-03-02 5:50 ` [PATCH 2/2] KVM: arm64: PMU: Don't save PMCR_EL0.{C,P} for the vCPU Reiji Watanabe
2023-03-02 5:50 ` Reiji Watanabe
2023-03-12 15:01 ` Marc Zyngier
2023-03-12 15:01 ` Marc Zyngier
2023-03-13 3:34 ` Reiji Watanabe
2023-03-13 3:34 ` Reiji Watanabe
2023-03-12 15:04 ` [PATCH 0/2] KVM: arm64: PMU: Preserve vPMC registers properly on migration Marc Zyngier
2023-03-12 15:04 ` Marc Zyngier
2023-03-13 3:35 ` Reiji Watanabe
2023-03-13 3:35 ` Reiji Watanabe
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=20230302055033.3081456-1-reijiw@google.com \
--to=reijiw@google.com \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=ricarkol@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.