From: Nitesh Narayan Lal <nitesh@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mtosatti@redhat.com, rkrcmar@redhat.com, vkuznets@redhat.com,
sean.j.christopherson@intel.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org
Subject: Re: [Patch v2 2/2] KVM: x86: deliver KVM IOAPIC scan request to target vCPUs
Date: Fri, 15 Nov 2019 06:45:52 -0500 [thread overview]
Message-ID: <26daac23-6605-07ee-48f1-f8941fc02f64@redhat.com> (raw)
In-Reply-To: <62be5025-374b-6837-77dd-05ab2148f295@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
On 11/15/19 5:26 AM, Paolo Bonzini wrote:
> On 07/11/19 13:53, Nitesh Narayan Lal wrote:
>> In IOAPIC fixed delivery mode instead of flushing the scan
>> requests to all vCPUs, we should only send the requests to
>> vCPUs specified within the destination field.
>>
>> This patch introduces kvm_get_dest_vcpus_mask() API which
>> retrieves an array of target vCPUs by using
>> kvm_apic_map_get_dest_lapic() and then based on the
>> vcpus_idx, it sets the bit in a bitmap. However, if the above
>> fails kvm_get_dest_vcpus_mask() finds the target vCPUs by
>> traversing all available vCPUs. Followed by setting the
>> bits in the bitmap.
> Queued, thanks. I just took the liberty of renaming the function to
> kvm_bitmap_or_dest_vcpus.
Sure, thank you.
>
> Paolo
>
--
Nitesh
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-11-15 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:53 [PATCH v2 0/2] KVM: deliver IOAPIC scan request only to the target vCPUs Nitesh Narayan Lal
2019-11-07 12:53 ` [Patch v2 1/2] KVM: remember position in kvm->vcpus array Nitesh Narayan Lal
2019-11-07 12:53 ` [Patch v2 2/2] KVM: x86: deliver KVM IOAPIC scan request to target vCPUs Nitesh Narayan Lal
2019-11-15 10:26 ` Paolo Bonzini
2019-11-15 11:45 ` Nitesh Narayan Lal [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=26daac23-6605-07ee-48f1-f8941fc02f64@redhat.com \
--to=nitesh@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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).