From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org, cohuck@redhat.com,
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: Tue, 12 Dec 2017 18:48:40 +0100 [thread overview]
Message-ID: <a5e37872-8a0c-8c9e-da04-7d3fb52cc9d3@redhat.com> (raw)
In-Reply-To: <d3decdf8-b029-f8f8-bdbe-40d68dc33814@redhat.com>
On 12/12/2017 18:47, David Hildenbrand wrote:
>> @@ -2547,13 +2547,13 @@ static long kvm_vcpu_ioctl(struct file *filp,
>> #if defined(CONFIG_S390) || defined(CONFIG_PPC) || defined(CONFIG_MIPS)
> can we now also get rid of this ugly define?
Not yet, I'd have to add the function to x86 and ARM, or a dummy inline.
Paolo
>> /*
>> * Special cases: vcpu ioctls that are asynchronous to vcpu execution,
>> - * so vcpu_load() would break it.
>> + * so mutex_lock() would break it.
>> */
>> - if (ioctl == KVM_S390_INTERRUPT || ioctl == KVM_S390_IRQ || ioctl == KVM_INTERRUPT)
>> - return kvm_arch_vcpu_ioctl(filp, ioctl, arg);
>> + r = kvm_arch_vcpu_async_ioctl(filp, ioctl, arg);
>> + if (r != -ENOIOCTLCMD)
>> + return r;
>> #endif
>>
>> -
> unrelated change but the right thing to do :)
>
next prev parent reply other threads:[~2017-12-12 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 17:31 Paolo Bonzini
2017-12-12 17:47 ` David Hildenbrand
2017-12-12 17:48 ` Paolo Bonzini [this message]
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
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=a5e37872-8a0c-8c9e-da04-7d3fb52cc9d3@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--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 \
/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
all inboxes | Powered by JetHome®