From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 643ACC4332F for ; Tue, 1 Feb 2022 13:48:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238876AbiBANsD (ORCPT ); Tue, 1 Feb 2022 08:48:03 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:39016 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230213AbiBANsB (ORCPT ); Tue, 1 Feb 2022 08:48:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643723280; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jvjdmFpP+aywoc255+AEdYPS7LfT6vlQYF3LS6kxF8U=; b=gkX2T1W7hHe1wJhAUR0+2nUAc69mh/EW3B1lYwNjyglH1H1G66kbdkfetldqMvXTxnwIIX Glv73Jxke8ATb53Hm7Kd/wyzL/WfF3Ll1gTdmw55WVSR3myiOZsSqe/wKHT5nNxNLCEyup d+HQsEhaO2hhxa0r5V29LRFwfcHhllA= Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-164-C4K_n8LMMtW1fgwDF6w_0A-1; Tue, 01 Feb 2022 08:48:00 -0500 X-MC-Unique: C4K_n8LMMtW1fgwDF6w_0A-1 Received: by mail-ed1-f69.google.com with SMTP id f21-20020a50d555000000b00407a8d03b5fso8639980edj.9 for ; Tue, 01 Feb 2022 05:47:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=jvjdmFpP+aywoc255+AEdYPS7LfT6vlQYF3LS6kxF8U=; b=Ht/zRirlvENX3Aw4W2dWQ0lg/DvLMt/3BIMybZqCYjmgruyB9cOxNW4gq6LYczBTFB PFSEsNQyT2pCVjWJn+Iei6CUjK38JLmEYR4uB+ij5XEzBex8vJkNPjbkMaom37Pv5KAC 0sXLGCdMbmVB3OdaTF/BjqbvAWYCZ/P6EHw8JXlgFlZ5SzOduuly2W93SvpmLvgzuKV9 Y7qPSfwH2YanA17HlpsPdo+6xR8foNWKHF9GBDpTudLigq2LFtXvnAs4DG/7yA0yOPm/ bBzyE8XVnJIy0I/UDicw6i/PJ0ss9fWnli9tfdp9m//Rke9v15TZ/lbnjhDIuKjgLhJN TMUA== X-Gm-Message-State: AOAM531ervckCUuIuHCGBUX5YjtXFv/YwqKoz9uzsK5HF6r+o+Mm6u5e XsmaF2DsHgDtCjVgoZUYoYn5lzxqbDHgzi4WfIifxvQvow0YzZ4z5/9qKWkFOcfXMNiI/IGygTg A/Ksz71jVy00eaB2MU6LENccv X-Received: by 2002:a05:6402:510b:: with SMTP id m11mr24890195edd.203.1643723278785; Tue, 01 Feb 2022 05:47:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJxrAn6f7jQ1xsfRbMafBTd7spTEbJU55+LKoGfzGdlknXLbTTVI9SS+8IKsUIyGryLogcl9+w== X-Received: by 2002:a05:6402:510b:: with SMTP id m11mr24890170edd.203.1643723278466; Tue, 01 Feb 2022 05:47:58 -0800 (PST) Received: from ?IPV6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.googlemail.com with ESMTPSA id z6sm14841091ejd.35.2022.02.01.05.47.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Feb 2022 05:47:57 -0800 (PST) Message-ID: Date: Tue, 1 Feb 2022 14:47:55 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v3 0/8] KVM: x86: Hyper-V hypercall fix and cleanups Content-Language: en-US To: Sean Christopherson , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Wei Liu , Dexuan Cui , Arnd Bergmann Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Ajay Garg References: <20211207220926.718794-1-seanjc@google.com> From: Paolo Bonzini In-Reply-To: <20211207220926.718794-1-seanjc@google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/7/21 23:09, Sean Christopherson wrote: > Fix a bug where KVM incorrectly skips an "all_cpus" IPI request, and misc > cleanups and enhancements for KVM handling of Hyper-V hypercalls. > > Based on kvm/queue, commit 1cf84614b04a ("KVM: x86: Exit to ..."). > > v3: > - Collect reviews. [Vitaly] > - Add BUILD_BUG_ON() to protect KVM_HV_MAX_SPARSE_VCPU_SET_BITS. [Vitaly] > - Fix misc typos. [Vitaly] > - Opportunistically rename "cnt" to "rep_cnt" in tracepoint. [Vitaly] > - Drop var_cnt checks for debug hypercalls due to lack of documentation > as to their expected behavior. [Vitaly] > - Tweak the changelog regarding the TLFS spec issue to reference the > bug filed by Vitaly. > > v2: https://lore.kernel.org/all/20211030000800.3065132-1-seanjc@google.com/ > > Sean Christopherson (8): > KVM: x86: Ignore sparse banks size for an "all CPUs", non-sparse IPI > req > KVM: x86: Get the number of Hyper-V sparse banks from the VARHEAD > field > KVM: x86: Refactor kvm_hv_flush_tlb() to reduce indentation > KVM: x86: Add a helper to get the sparse VP_SET for IPIs and TLB > flushes > KVM: x86: Don't bother reading sparse banks that end up being ignored > KVM: x86: Shove vp_bitmap handling down into sparse_set_to_vcpu_mask() > KVM: x86: Reject fixeds-size Hyper-V hypercalls with non-zero > "var_cnt" > KVM: x86: Add checks for reserved-to-zero Hyper-V hypercall fields > > arch/x86/kvm/hyperv.c | 175 ++++++++++++++++++------------ > arch/x86/kvm/trace.h | 14 ++- > include/asm-generic/hyperv-tlfs.h | 7 ++ > 3 files changed, 123 insertions(+), 73 deletions(-) > Queued 2-8, thanks. Paolo