From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org, christoffer.dall@linaro.org,
James Hogan <jhogan@kernel.org>,
Paul Mackerras <paulus@ozlabs.org>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] KVM: introduce kvm_arch_vcpu_async_ioctl
Date: Wed, 13 Dec 2017 09:47:55 +0100 [thread overview]
Message-ID: <20171213094755.428f8f26.cohuck@redhat.com> (raw)
In-Reply-To: <1513099915-107126-1-git-send-email-pbonzini@redhat.com>
On Tue, 12 Dec 2017 18:31:55 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> After the vcpu_load/vcpu_put pushdown, the handling of asynchronous VCPU
> ioctl is already much clearer in that it is obvious that they bypass
> vcpu_load and vcpu_put.
>
> However, it is still not perfect in that the different state of the VCPU
> mutex is still hidden in the caller. Separate those ioctls into a new
> function kvm_arch_vcpu_async_ioctl that returns -ENOIOCTLCMD for more
> "traditional" synchronous ioctls.
>
> Cc: James Hogan <jhogan@kernel.org>
> Cc: Paul Mackerras <paulus@ozlabs.org>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Suggested-by: Cornelia Huck <cohuck@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/mips/kvm/mips.c | 15 ++++++++++++---
> arch/powerpc/kvm/powerpc.c | 14 +++++++++++---
> arch/s390/kvm/kvm-s390.c | 16 ++++++++++++----
> include/linux/kvm_host.h | 2 ++
> virt/kvm/kvm_main.c | 8 ++++----
> 5 files changed, 41 insertions(+), 14 deletions(-)
Another vote for a dummy function here, but otherwise
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
prev parent reply other threads:[~2017-12-13 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 17:31 [PATCH] KVM: introduce kvm_arch_vcpu_async_ioctl Paolo Bonzini
2017-12-12 17:47 ` David Hildenbrand
2017-12-12 17:48 ` Paolo Bonzini
2017-12-12 17:59 ` David Hildenbrand
2017-12-12 18:25 ` Christoffer Dall
2017-12-13 9:31 ` Paolo Bonzini
2017-12-12 18:42 ` Christian Borntraeger
2017-12-13 8:47 ` Cornelia Huck [this message]
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=20171213094755.428f8f26.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=jhogan@kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
/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