From: Oliver Upton <oupton@google.com>
To: kvmarm@lists.cs.columbia.edu
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Peter Shier <pshier@google.com>,
Shakeel Butt <shakeelb@google.com>,
Guangyu Shi <guangyus@google.com>,
Oliver Upton <oupton@google.com>
Subject: [PATCH 0/3] KVM: arm64: Use generic guest entry infrastructure
Date: Thu, 29 Jul 2021 19:56:29 +0000 [thread overview]
Message-ID: <20210729195632.489978-1-oupton@google.com> (raw)
The arm64 kernel doesn't yet support the full generic entry
infrastructure. That being said, KVM/arm64 doesn't properly handle
TIF_NOTIFY_RESUME and could pick this up by switching to the generic
guest entry infrasturture.
Patch 1 adds a missing vCPU stat to ARM64 to record the number of signal
exits to userspace.
Patch 2 unhitches entry-kvm from entry-generic, as ARM64 doesn't
currently support the generic infrastructure.
Patch 3 replaces the open-coded entry handling with the generic xfer
function.
This series was tested on an Ampere Mt. Jade reference system. The
series cleanly applies to kvm/queue (note that this is deliberate as the
generic kvm stats patches have not yet propagated to kvm-arm/queue) at
the following commit:
8ad5e63649ff ("KVM: Don't take mmu_lock for range invalidation unless necessary")
Oliver Upton (3):
KVM: arm64: Record number of signal exits as a vCPU stat
entry: KVM: Allow use of generic KVM entry w/o full generic support
KVM: arm64: Use generic KVM xfer to guest work function
arch/arm64/include/asm/kvm_host.h | 1 +
arch/arm64/kvm/Kconfig | 1 +
arch/arm64/kvm/arm.c | 26 ++++++++++++++------------
arch/arm64/kvm/guest.c | 3 ++-
include/linux/entry-kvm.h | 6 +++++-
5 files changed, 23 insertions(+), 14 deletions(-)
--
2.32.0.554.ge1b32706d8-goog
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oupton@google.com>
To: kvmarm@lists.cs.columbia.edu
Cc: Shakeel Butt <shakeelb@google.com>,
kvm@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Marc Zyngier <maz@kernel.org>, Peter Shier <pshier@google.com>,
linux-kernel@vger.kernel.org, Guangyu Shi <guangyus@google.com>,
Will Deacon <will@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] KVM: arm64: Use generic guest entry infrastructure
Date: Thu, 29 Jul 2021 19:56:29 +0000 [thread overview]
Message-ID: <20210729195632.489978-1-oupton@google.com> (raw)
The arm64 kernel doesn't yet support the full generic entry
infrastructure. That being said, KVM/arm64 doesn't properly handle
TIF_NOTIFY_RESUME and could pick this up by switching to the generic
guest entry infrasturture.
Patch 1 adds a missing vCPU stat to ARM64 to record the number of signal
exits to userspace.
Patch 2 unhitches entry-kvm from entry-generic, as ARM64 doesn't
currently support the generic infrastructure.
Patch 3 replaces the open-coded entry handling with the generic xfer
function.
This series was tested on an Ampere Mt. Jade reference system. The
series cleanly applies to kvm/queue (note that this is deliberate as the
generic kvm stats patches have not yet propagated to kvm-arm/queue) at
the following commit:
8ad5e63649ff ("KVM: Don't take mmu_lock for range invalidation unless necessary")
Oliver Upton (3):
KVM: arm64: Record number of signal exits as a vCPU stat
entry: KVM: Allow use of generic KVM entry w/o full generic support
KVM: arm64: Use generic KVM xfer to guest work function
arch/arm64/include/asm/kvm_host.h | 1 +
arch/arm64/kvm/Kconfig | 1 +
arch/arm64/kvm/arm.c | 26 ++++++++++++++------------
arch/arm64/kvm/guest.c | 3 ++-
include/linux/entry-kvm.h | 6 +++++-
5 files changed, 23 insertions(+), 14 deletions(-)
--
2.32.0.554.ge1b32706d8-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oupton@google.com>
To: kvmarm@lists.cs.columbia.edu
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Peter Shier <pshier@google.com>,
Shakeel Butt <shakeelb@google.com>,
Guangyu Shi <guangyus@google.com>,
Oliver Upton <oupton@google.com>
Subject: [PATCH 0/3] KVM: arm64: Use generic guest entry infrastructure
Date: Thu, 29 Jul 2021 19:56:29 +0000 [thread overview]
Message-ID: <20210729195632.489978-1-oupton@google.com> (raw)
The arm64 kernel doesn't yet support the full generic entry
infrastructure. That being said, KVM/arm64 doesn't properly handle
TIF_NOTIFY_RESUME and could pick this up by switching to the generic
guest entry infrasturture.
Patch 1 adds a missing vCPU stat to ARM64 to record the number of signal
exits to userspace.
Patch 2 unhitches entry-kvm from entry-generic, as ARM64 doesn't
currently support the generic infrastructure.
Patch 3 replaces the open-coded entry handling with the generic xfer
function.
This series was tested on an Ampere Mt. Jade reference system. The
series cleanly applies to kvm/queue (note that this is deliberate as the
generic kvm stats patches have not yet propagated to kvm-arm/queue) at
the following commit:
8ad5e63649ff ("KVM: Don't take mmu_lock for range invalidation unless necessary")
Oliver Upton (3):
KVM: arm64: Record number of signal exits as a vCPU stat
entry: KVM: Allow use of generic KVM entry w/o full generic support
KVM: arm64: Use generic KVM xfer to guest work function
arch/arm64/include/asm/kvm_host.h | 1 +
arch/arm64/kvm/Kconfig | 1 +
arch/arm64/kvm/arm.c | 26 ++++++++++++++------------
arch/arm64/kvm/guest.c | 3 ++-
include/linux/entry-kvm.h | 6 +++++-
5 files changed, 23 insertions(+), 14 deletions(-)
--
2.32.0.554.ge1b32706d8-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:[~2021-07-29 19:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 19:56 Oliver Upton [this message]
2021-07-29 19:56 ` [PATCH 0/3] KVM: arm64: Use generic guest entry infrastructure Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 19:56 ` [PATCH 1/3] KVM: arm64: Record number of signal exits as a vCPU stat Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 20:07 ` Jing Zhang
2021-07-29 20:07 ` Jing Zhang
2021-07-29 20:07 ` Jing Zhang
2021-07-29 20:23 ` Oliver Upton
2021-07-29 20:23 ` Oliver Upton
2021-07-29 20:23 ` Oliver Upton
2021-07-29 19:56 ` [PATCH 2/3] entry: KVM: Allow use of generic KVM entry w/o full generic support Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 19:56 ` [PATCH 3/3] KVM: arm64: Use generic KVM xfer to guest work function Oliver Upton
2021-07-29 19:56 ` Oliver Upton
2021-07-29 19:56 ` 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=20210729195632.489978-1-oupton@google.com \
--to=oupton@google.com \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=guangyus@google.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=pshier@google.com \
--cc=shakeelb@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--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 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.