linux-kernel - Re: [PATCH v4 0/5] KVM: x86: hyperv: PV IPI support for Windows guests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87tvoqrxxb.fsf@vitty.brq.redhat.com>
Date:   Mon, 23 Jul 2018 13:31:12 +0200
From:   Vitaly Kuznetsov <vkuznets@...hat.com>
To:     kvm@...r.kernel.org
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        Roman Kagan <rkagan@...tuozzo.com>,
        "K. Y. Srinivasan" <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        "Michael Kelley \(EOSG\)" <Michael.H.Kelley@...rosoft.com>,
        Mohammed Gamal <mmorsy@...hat.com>,
        Cathy Avery <cavery@...hat.com>,
        Wanpeng Li <wanpeng.li@...mail.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/5] KVM: x86: hyperv: PV IPI support for Windows guests

Vitaly Kuznetsov <vkuznets@...hat.com> writes:

> Changes since v3 [Roman Kagan]:
> - Don't use vcpu_id in kvm_make_vcpus_request_mask to avoid dealing with
>   sparse CPU masks.
> - Create get_vcpu_idx_by_vpidx() and use it in get_vcpu_by_vpidx() and
>   kvm_hv_flush_tlb().
>
> Using hypercall for sending IPIs is faster because this allows to specify
> any number of vCPUs (even > 64 with sparse CPU set), the whole procedure
> will take only one VMEXIT.
>
> Same as PV TLB flush, this allows Windows guests having > 64 vCPUs to boot
> on KVM when Hyper-V extensions are enabled.

Ping)

-- 
  Vitaly