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 B0669C433F5 for ; Mon, 16 May 2022 21:08:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349155AbiEPVIs (ORCPT ); Mon, 16 May 2022 17:08:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56492 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349204AbiEPVIN (ORCPT ); Mon, 16 May 2022 17:08:13 -0400 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF1EB4A3E7 for ; Mon, 16 May 2022 13:49:56 -0700 (PDT) Received: by mail-pl1-x634.google.com with SMTP id q4so15564522plr.11 for ; Mon, 16 May 2022 13:49:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=KrZd1d7ZW1bFcikModx6EkxPFI/wL98ky5uKMz/aH5s=; b=MONmx06zlMIYc3wCFtScWn/8i4RuJ7ZboFJ76kZhENs65e+45QZ9TJiv8sWMkWiH3i oMf04Udsv5xFLVu8pZE6Oi957vt5/1YMSwrOFXbdWqCnWjD3OiHE+stQXPhVfLhrNtUD YTr/FlydzldOfEek6k+R0YmmIbjNWSeIWc99Arc2CAig9n+ZY1W3JXsqnHmHZaOU+rce sCdtaAQuzebqWxJEffXBMZkzQ+FIg8wmEWPNFp/6+5tC0BpkpszO707w1tYwG2vRUQHs 4XzCsZAs3Lm+5PtNS0cv7POMWbi8quYX8ck/U6lsOwQ8TanCa4cAzne213tIRV4+xwlF Ntwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=KrZd1d7ZW1bFcikModx6EkxPFI/wL98ky5uKMz/aH5s=; b=W5j6YwrQMzZZ9MDNtbKRJbBJaZD4/VvDAVuHoacmhEdAv0DVNy8goEuTxHDNSB7lvV Z9TAI5LLhLcemdL7TRRiBBfTHPCCJhbBoNKvu7Afn0R4IfLmgszYR+phZCcGG5GIcKZ3 Z95nn4JzTQaYoBNva2zHfraTvmxnSi9muDt0k6wgDUVt6YX2pnh5pdyYVA+PytcLXpf7 VlOHD4xmf+YWWo5pNrJ1lalR4N5MQZaT8NodtSamMfj7rsgiSgMBdE1jnNB2u9mHQ5Vr xcfboFNuz850q3bkHLWri1/p5rDDoeoZejxyCk3auq77rI2ubgGa2jG+0eymqsFM6wLe aM3A== X-Gm-Message-State: AOAM5305ZWUAHF9l849CCo7YTmRLK5W8zYUrhGUDs7xon5wQCyWG+T24 ebZ+8XmoWDpgrrP4byJtUB0hVA== X-Google-Smtp-Source: ABdhPJyfN+D2uao0MqY3oPEXUKmvH4qWuWl1YZgKcJeE6F9PV+VJP4kEuxpIbb6adk0PONfl+dMizw== X-Received: by 2002:a17:902:e94e:b0:15b:22a7:f593 with SMTP id b14-20020a170902e94e00b0015b22a7f593mr19047116pll.148.1652734196312; Mon, 16 May 2022 13:49:56 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id n12-20020a1709026a8c00b0015ea9aabd19sm7372503plk.241.2022.05.16.13.49.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 May 2022 13:49:55 -0700 (PDT) Date: Mon, 16 May 2022 20:49:52 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: Zeng Guang , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , "kvm@vger.kernel.org" , Dave Hansen , "Luck, Tony" , Kan Liang , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Kim Phillips , Jarkko Sakkinen , Jethro Beekman , "Huang, Kai" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "Hu, Robert" , "Gao, Chao" Subject: Re: [PATCH v9 0/9] IPI virtualization support for VM Message-ID: References: <20220419153155.11504-1-guang.zeng@intel.com> <2d33b71a-13e5-d377-abc2-c20958526497@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 03, 2022, Paolo Bonzini wrote: > On 5/3/22 09:32, Zeng Guang wrote: > > > > I don't see "[PATCH v9 4/9] KVM: VMX: Report tertiary_exec_control field in > > dump_vmcs()" in kvm/queue. Does it not need ? > > Added now (somehow the patches were not threaded, so I had to catch them one > by one from lore). > > > Selftests for KVM_CAP_MAX_VCPU_ID is posted in V2 which is revised on top of > > kvm/queue. > > ([PATCH v2] kvm: selftests: Add KVM_CAP_MAX_VCPU_ID cap test - Zeng > > Guang (kernel.org) ) > > Queued, thanks. Shouldn't we have a solution for the read-only APIC_ID mess before this is merged?