From: Andrew Scull <ascull@google.com>
To: kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, kernel-team@android.com, dave.martin@arm.com
Subject: [PATCH 0/2] Manage vcpu flags from the host
Date: Fri, 10 Jul 2020 10:57:52 +0100 [thread overview]
Message-ID: <20200710095754.3641976-1-ascull@google.com> (raw)
This is a clean up and no functional change is intended.
The aim is to keep management of the flags in the host and out of hyp. I
find this makes it easier to understand how the flags are used.
This is the result of a previous thread with Dave where it was explained
that there is an intent to synchronize the flags in clearly defined
places <20200707145713.287710-1-ascull@google.com>
Andrew Scull (2):
KVM: arm64: Leave KVM_ARM64_DEBUG_DIRTY updates to the host
KVM: arm64: Leave vcpu FPSIMD synchronization in host
arch/arm64/include/asm/kvm_host.h | 7 ++-
arch/arm64/kvm/arm.c | 4 +-
arch/arm64/kvm/debug.c | 2 +
arch/arm64/kvm/fpsimd.c | 57 ++++++++++++++++-------
arch/arm64/kvm/hyp/include/hyp/debug-sr.h | 2 -
arch/arm64/kvm/hyp/include/hyp/switch.h | 19 --------
arch/arm64/kvm/hyp/nvhe/switch.c | 3 +-
arch/arm64/kvm/hyp/vhe/switch.c | 3 +-
8 files changed, 51 insertions(+), 46 deletions(-)
--
2.27.0.383.g050319c2ae-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2020-07-10 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 9:57 Andrew Scull [this message]
2020-07-10 9:57 ` [PATCH 1/2] KVM: arm64: Leave KVM_ARM64_DEBUG_DIRTY updates to the host Andrew Scull
2020-07-10 9:57 ` [PATCH 2/2] KVM: arm64: Leave vcpu FPSIMD synchronization in host Andrew Scull
2020-07-13 16:04 ` Dave Martin
2020-07-13 20:42 ` Andrew Scull
2020-07-14 16:17 ` Dave Martin
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=20200710095754.3641976-1-ascull@google.com \
--to=ascull@google.com \
--cc=dave.martin@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@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