> -----Original Message-----
> From: Vitaly Kuznetsov <vkuzn...@redhat.com>
> Sent: Thursday, June 28, 2018 8:05 AM
> To: Wanpeng Li <kernel...@gmail.com>
> Cc: Radim Krcmar <rkrc...@redhat.com>; kvm <k...@vger.kernel.org>;
> Paolo Bonzini <pbonz...@redhat.com>; Roman Kagan
> <rka...@virtuozzo.com>; KY Srinivasan <k...@microsoft.com>; Haiyang
> Zhang <haiya...@microsoft.com>; Stephen Hemminger
> <sthem...@microsoft.com>; Michael Kelley (EOSG)
> <michael.h.kel...@microsoft.com>; Mohammed Gamal
> <mmo...@redhat.com>; Cathy Avery <cav...@redhat.com>; LKML <linux-
> ker...@vger.kernel.org>
> Subject: Re: [PATCH 3/3] KVM: x86: hyperv: implement PV IPI send
> hypercalls
>
> Wanpeng Li <kernel...@gmail.com> writes:
>
> > Hi Paolo and Radim,
> >
> > I have already completed the patches for linux guest/kvm/qemu w/ vCPUs
> > <= 64, however, extra complication as the ex in hyperv should be
> > introduced for vCPUs > 64, so do you think vCPU <=64 is enough for
> > linux guest or should me introduce two hypercall as what hyperv does
> > w/ ex logic?
> >
>
> Neither Paolo nor Radim but as we already have
> #define KVM_MAX_VCPUS 288
> on at least x86, supporting <= 64 vCPUs seems to be too limiting for any
> new functionality.
Agreed.
K. Y
>
> --
> Vitaly
