linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Fuad Tabba <tabba@google.com>
To: kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, will@kernel.org, qperret@google.com,
	james.morse@arm.com,  alexandru.elisei@arm.com,
	suzuki.poulose@arm.com, catalin.marinas@arm.com,
	 drjones@redhat.com, linux-arm-kernel@lists.infradead.org,
	tabba@google.com, kernel-team@android.com
Subject: [PATCH v1 0/3] KVM: arm64: Do not communicate host pmu event changes by accessing hyp data
Date: Fri,  8 Apr 2022 09:40:49 +0100	[thread overview]
Message-ID: <20220408084052.3310931-1-tabba@google.com> (raw)

Hi,

This series changes the way KVM communicates host pmu event changes to the
hypervisor in nvhe and protected mode. Instead of accessing hyp data directly
from the host, the data is passed to hyp via the loaded vcpu. This gives more
isolation between the host and the hypervisor, and would allow us to use pmu in
protected mode.

This series is based on kvmarm/next.

Thanks,
/fuad

Fuad Tabba (3):
  KVM: arm64: Wrapper for getting pmu_events
  KVM: arm64: Pass pmu events to hyp via vcpu
  KVM: arm64: Reenable pmu in Protected Mode

 arch/arm64/include/asm/kvm_host.h |  8 ++----
 arch/arm64/kvm/arm.c              |  2 +-
 arch/arm64/kvm/hyp/nvhe/switch.c  | 20 ++++---------
 arch/arm64/kvm/pmu-emul.c         |  3 +-
 arch/arm64/kvm/pmu.c              | 48 ++++++++++++++++++++-----------
 include/kvm/arm_pmu.h             |  6 ++++
 6 files changed, 47 insertions(+), 40 deletions(-)


base-commit: 21ea457842759a236eefed2cfaa8cc7e5dc967a0
-- 
2.35.1.1178.g4f1659d476-goog


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-04-08  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  8:40 Fuad Tabba [this message]
2022-04-08  8:40 ` [PATCH v1 1/3] KVM: arm64: Wrapper for getting pmu_events Fuad Tabba
2022-04-08  8:40 ` [PATCH v1 2/3] KVM: arm64: Pass pmu events to hyp via vcpu Fuad Tabba
2022-05-05  9:00   ` Marc Zyngier
2022-05-06 13:57     ` Fuad Tabba
2022-04-08  8:40 ` [PATCH v1 3/3] KVM: arm64: Reenable pmu in Protected Mode Fuad Tabba

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=20220408084052.3310931-1-tabba@google.com \
    --to=tabba@google.com \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=drjones@redhat.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).