From: Paolo Bonzini <pbonzini@redhat.com>
To: wei.guo.simon@gmail.com, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH] KVM: surround kvm_arch_vcpu_async_ioctl() with #ifdef
Date: Wed, 28 Feb 2018 07:53:33 +0100 [thread overview]
Message-ID: <19e68ff8-552e-2e64-c2e4-3c718343bf57@redhat.com> (raw)
In-Reply-To: <1519785099-13808-1-git-send-email-wei.guo.simon@gmail.com>
On 28/02/2018 03:31, wei.guo.simon@gmail.com wrote:
> From: Simon Guo <wei.guo.simon@gmail.com>
>
> Although CONFIG_HAVE_KVM_VCPU_ASYNC_IOCTL is usually on, logically
> kvm_arch_vcpu_async_ioctl() definition should be wrapped with
> CONFIG_HAVE_KVM_VCPU_ASYNC_IOCTL #ifdef.
No, the symbol is defined by Kconfig. It is a bug if it is not #defined.
Paolo
> This patch adds the #ifdef surround.
>
> Signed-off-by: Simon Guo <wei.guo.simon@gmail.com>
> ---
> arch/mips/kvm/mips.c | 2 ++
> arch/powerpc/kvm/powerpc.c | 2 ++
> arch/s390/kvm/kvm-s390.c | 2 ++
> 3 files changed, 6 insertions(+)
>
> diff --git a/arch/mips/kvm/mips.c b/arch/mips/kvm/mips.c
> index 2549fdd..4d593e5 100644
> --- a/arch/mips/kvm/mips.c
> +++ b/arch/mips/kvm/mips.c
> @@ -903,6 +903,7 @@ static int kvm_vcpu_ioctl_enable_cap(struct kvm_vcpu *vcpu,
> return r;
> }
>
> +#ifdef CONFIG_HAVE_KVM_VCPU_ASYNC_IOCTL
> long kvm_arch_vcpu_async_ioctl(struct file *filp, unsigned int ioctl,
> unsigned long arg)
> {
> @@ -922,6 +923,7 @@ long kvm_arch_vcpu_async_ioctl(struct file *filp, unsigned int ioctl,
>
> return -ENOIOCTLCMD;
> }
> +#endif
>
> long kvm_arch_vcpu_ioctl(struct file *filp, unsigned int ioctl,
> unsigned long arg)
> diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
> index 403e642..2adca3c 100644
> --- a/arch/powerpc/kvm/powerpc.c
> +++ b/arch/powerpc/kvm/powerpc.c
> @@ -1757,6 +1757,7 @@ int kvm_arch_vcpu_ioctl_set_mpstate(struct kvm_vcpu *vcpu,
> return -EINVAL;
> }
>
> +#ifdef CONFIG_HAVE_KVM_VCPU_ASYNC_IOCTL
> long kvm_arch_vcpu_async_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
> {
> @@ -1771,6 +1772,7 @@ long kvm_arch_vcpu_async_ioctl(struct file *filp,
> }
> return -ENOIOCTLCMD;
> }
> +#endif
>
> long kvm_arch_vcpu_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 77d7818..c499396 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -3784,6 +3784,7 @@ static long kvm_s390_guest_mem_op(struct kvm_vcpu *vcpu,
> return r;
> }
>
> +#ifdef CONFIG_HAVE_KVM_VCPU_ASYNC_IOCTL
> long kvm_arch_vcpu_async_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
> {
> @@ -3811,6 +3812,7 @@ long kvm_arch_vcpu_async_ioctl(struct file *filp,
> }
> return -ENOIOCTLCMD;
> }
> +#endif
>
> long kvm_arch_vcpu_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
>
prev parent reply other threads:[~2018-02-28 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 2:31 [PATCH] KVM: surround kvm_arch_vcpu_async_ioctl() with #ifdef wei.guo.simon
2018-02-28 6:53 ` Paolo Bonzini [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=19e68ff8-552e-2e64-c2e4-3c718343bf57@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wei.guo.simon@gmail.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;
as well as URLs for NNTP newsgroup(s).