From: david@redhat.com (David Hildenbrand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/15] Move vcpu_load and vcpu_put calls to arch code
Date: Tue, 28 Nov 2017 21:55:20 +0100 [thread overview]
Message-ID: <dd738b4f-3d99-ec3b-fa5e-d166230f9d2b@redhat.com> (raw)
In-Reply-To: <20171125205718.7731-1-christoffer.dall@linaro.org>
On 25.11.2017 21:57, Christoffer Dall wrote:
> Some architectures may decide to do different things during
> kvm_arch_vcpu_load depending on the ioctl being executed. For example,
> arm64 is about to do significant work in vcpu load/put when running a
> vcpu, but it's problematic to do this for any other vcpu ioctl than
> KVM_RUN.
>
> Further, while it may be possible to call kvm_arch_vcpu_load() for a
> number of non-KVM_RUN ioctls, it makes the KVM/ARM code more difficult
> to reason about, especially after my optimization series, because a lot
> of things can now happen, where we have to consider if we're really in
> the process of running a vcpu or not.
>
> This series will first move the vcpu_load() and vcpu_put() calls in the
> arch generic dispatch function into each case of the switch statement
> and then, one-by-one, pushed the calls down into the architecture
> specific code making the changes for each ioctl as required.
>
> Thanks,
> -Christoffer
>
> Christoffer Dall (15):
> KVM: Prepare for moving vcpu_load/vcpu_put into arch specific code
> KVM: Factor out vcpu->pid adjustment for KVM_RUN
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_run
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_regs
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_regs
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_sregs
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_sregs
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_mpstate
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_mpstate
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_translate
> KVM: Move vcpu_load to arch-specific
> kvm_arch_vcpu_ioctl_set_guest_debug
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_fpu
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_fpu
> KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl
> KVM: arm/arm64: Avoid vcpu_load for other vcpu ioctls than KVM_RUN
>
> arch/arm64/kvm/guest.c | 17 +++++--
> arch/mips/kvm/mips.c | 72 +++++++++++++++++++--------
> arch/powerpc/kvm/book3s.c | 38 +++++++++++++-
> arch/powerpc/kvm/booke.c | 65 +++++++++++++++++++-----
> arch/powerpc/kvm/powerpc.c | 24 ++++++---
> arch/s390/kvm/kvm-s390.c | 119 +++++++++++++++++++++++++++++++++++++-------
> arch/x86/kvm/x86.c | 121 ++++++++++++++++++++++++++++++++++++++-------
> include/linux/kvm_host.h | 2 +
> virt/kvm/arm/arm.c | 91 +++++++++++++++++++++++++---------
> virt/kvm/kvm_main.c | 43 +++++++---------
> 10 files changed, 463 insertions(+), 129 deletions(-)
>
Looking at the amount of code we duplicate, I wonder if simple ifdefery
(if possible) would be easier for the single known "special" case.
(most probably an unpopular opinion :) )
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2017-11-28 20:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 20:57 [PATCH 00/15] Move vcpu_load and vcpu_put calls to arch code Christoffer Dall
2017-11-25 20:57 ` [PATCH 01/15] KVM: Prepare for moving vcpu_load/vcpu_put into arch specific code Christoffer Dall
2017-11-27 16:53 ` Paolo Bonzini
2017-11-27 19:58 ` Christoffer Dall
2017-11-27 20:55 ` Paolo Bonzini
2017-11-25 20:57 ` [PATCH 02/15] KVM: Factor out vcpu->pid adjustment for KVM_RUN Christoffer Dall
2017-11-25 20:57 ` [PATCH 03/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_run Christoffer Dall
2017-11-25 20:57 ` [PATCH 04/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_regs Christoffer Dall
2017-11-25 20:57 ` [PATCH 05/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_regs Christoffer Dall
2017-11-25 20:57 ` [PATCH 06/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_sregs Christoffer Dall
2017-11-25 20:57 ` [PATCH 07/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_sregs Christoffer Dall
2017-11-25 20:57 ` [PATCH 08/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_mpstate Christoffer Dall
2017-11-25 20:57 ` [PATCH 09/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_mpstate Christoffer Dall
2017-11-25 20:57 ` [PATCH 10/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_translate Christoffer Dall
2017-11-25 20:57 ` [PATCH 11/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_guest_debug Christoffer Dall
2017-11-27 19:28 ` Christoffer Dall
2017-11-25 20:57 ` [PATCH 12/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_get_fpu Christoffer Dall
2017-11-25 20:57 ` [PATCH 13/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl_set_fpu Christoffer Dall
2017-11-25 20:57 ` [PATCH 14/15] KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl Christoffer Dall
2017-11-26 9:09 ` Christoffer Dall
2017-11-25 20:57 ` [PATCH 15/15] KVM: arm/arm64: Avoid vcpu_load for other vcpu ioctls than KVM_RUN Christoffer Dall
2017-11-26 9:11 ` [PATCH 00/15] Move vcpu_load and vcpu_put calls to arch code Christoffer Dall
2017-11-28 20:55 ` David Hildenbrand [this message]
2017-11-28 21:29 ` Paolo Bonzini
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=dd738b4f-3d99-ec3b-fa5e-d166230f9d2b@redhat.com \
--to=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).