From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH 2/2] KVM: X86: Implement PV send IPI support
Date: Fri, 29 Jun 2018 12:48:59 +0200 [thread overview]
Message-ID: <7d2b34ad-2436-0cee-3e71-97ea2eb5fd49@redhat.com> (raw)
In-Reply-To: <878t6xewei.fsf@vitty.brq.redhat.com>
On 29/06/2018 12:09, Vitaly Kuznetsov wrote:
>> +KVM_FEATURE_PV_SEND_IPI || 11 || guest checks this feature bit
>> + || || before enabling paravirtualized
>> + || || send IPIs.
> In case we decide to apply this as-is we'll likely need a new feature
> for PV IPI with > 64 vCPUs (or how else would the guest know if the host
> is capable or not?)
>
Yes, it makes sense. Perhaps we can do one of the following, or both:
1) add an argument for a "base vCPU id", so that you can use the
hypercall to send the IPI to CPUs 64..127, 128..191 etc.
2) have two bitmask arguments so that one hypercall handles 128 vCPUs.
to remove or limit the need for the more generic hypercall.
Paolo
next prev parent reply other threads:[~2018-06-29 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 9:51 [PATCH 0/2] KVM: x86: Add PV IPIs support Wanpeng Li
2018-06-29 9:51 ` [PATCH 1/2] KVM: X86: Implement PV IPI in linux guest Wanpeng Li
2018-06-29 10:10 ` Vitaly Kuznetsov
2018-06-30 10:04 ` Wanpeng Li
2018-06-29 11:22 ` kbuild test robot
2018-06-29 13:01 ` kbuild test robot
2018-06-29 9:51 ` [PATCH 2/2] KVM: X86: Implement PV send IPI support Wanpeng Li
2018-06-29 10:09 ` Vitaly Kuznetsov
2018-06-29 10:48 ` Paolo Bonzini [this message]
2018-06-30 10:05 ` Wanpeng Li
2018-06-29 10:45 ` Paolo Bonzini
2018-06-30 10:04 ` Wanpeng Li
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=7d2b34ad-2436-0cee-3e71-97ea2eb5fd49@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@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;
as well as URLs for NNTP newsgroup(s).