From: Dave Martin <Dave.Martin@arm.com>
To: Andrew Scull <ascull@google.com>
Cc: maz@kernel.org, kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2 0/4] Manage vcpu flags from the host
Date: Wed, 22 Jul 2020 17:24:30 +0100 [thread overview]
Message-ID: <20200722162429.GP30452@arm.com> (raw)
In-Reply-To: <20200713210505.2959828-1-ascull@google.com>
On Mon, Jul 13, 2020 at 10:05:01PM +0100, Andrew Scull wrote:
> The aim is to keep management of the flags in the host and out of hyp
> where possible. I find this makes it easier to understand how the flags
> are used as the responsibilities are clearly divided.
>
> The series applies on top of kvmarm/next after VHE and nVHE have been
> separated.
(A commit ID would be useful for someone trying to the patches.)
> From v1 <20200710095754.3641976-1-ascull@google.com>:
(Nit: Is there some easy way of looking up mails by Message-ID?
Otherwise, it can be helpful to have a mail archive URL here, e.g.,
lore.kernel.org)
> - Split FP change into smaller patches
> - Addressed Dave's other comments
>
> Andrew Scull (4):
> KVM: arm64: Leave KVM_ARM64_DEBUG_DIRTY updates to the host
> KVM: arm64: Predicate FPSIMD vcpu flags on feature support
> KVM: arm64: Leave vcpu FPSIMD synchronization in host
> KVM: arm64: Stop mapping host task thread flags to hyp
>
> 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 | 54 ++++++++++++++++-------
> 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, 48 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
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-07-22 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:05 [PATCH v2 0/4] Manage vcpu flags from the host Andrew Scull
2020-07-13 21:05 ` [PATCH v2 1/4] KVM: arm64: Leave KVM_ARM64_DEBUG_DIRTY updates to " Andrew Scull
2020-07-22 16:24 ` Dave Martin
2020-07-13 21:05 ` [PATCH v2 2/4] KVM: arm64: Predicate FPSIMD vcpu flags on feature support Andrew Scull
2020-07-22 16:23 ` Dave Martin
2020-07-13 21:05 ` [PATCH v2 3/4] KVM: arm64: Leave vcpu FPSIMD synchronization in host Andrew Scull
2020-07-22 16:24 ` Dave Martin
2020-07-13 21:05 ` [PATCH v2 4/4] KVM: arm64: Stop mapping host task thread flags to hyp Andrew Scull
2020-07-22 16:24 ` Dave Martin
2020-07-22 16:24 ` Dave Martin [this message]
2020-07-22 16:36 ` [PATCH v2 0/4] Manage vcpu flags from the host Marc Zyngier
2020-07-22 16:40 ` 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=20200722162429.GP30452@arm.com \
--to=dave.martin@arm.com \
--cc=ascull@google.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 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.