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 60304C636D3 for ; Wed, 1 Feb 2023 22:39:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231572AbjBAWjk (ORCPT ); Wed, 1 Feb 2023 17:39:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55480 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230136AbjBAWjg (ORCPT ); Wed, 1 Feb 2023 17:39:36 -0500 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2DBD0244B8 for ; Wed, 1 Feb 2023 14:39:35 -0800 (PST) Received: by mail-pl1-x64a.google.com with SMTP id m12-20020a1709026bcc00b001963da9cc71so246plt.11 for ; Wed, 01 Feb 2023 14:39:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=amcATFasBpSs8MNI2KZjvtTtDn1HGc2e896fYt2Kp/8=; b=fVkLjhI/esXpbr02/JFz7657iuPwZG4MSprxP6l5IuHndZRem6MmzG057TF7jg0QRr avSuRmiXhX/a/Ol7wmMrrAQiEBRm+z2BzZx4DV28cq43XKZKmq7RzNqWGHwRPZCmr7p6 ielRxk3KfClrtPfQdCIqOp7hZB9APb5BTdiNZvC6HovuBe0PR0MYbUCPqJLuteku0oka PtA2LezI9Mzc76mhc2ICYpfa0Yd5TlPiVluZAECJWOkP3ZBAkqTxxyVG/KgMplgkW4cY 6lj3QA1s9BjogDLlBbV3ZIBWUvzl4XFTfxwTNNa+dwSM8AyjiTIwmHEukY4M4i97GPtG K18A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=amcATFasBpSs8MNI2KZjvtTtDn1HGc2e896fYt2Kp/8=; b=ugVDqBzqDncFuRfzkLwbdFBn19zdDf2+n3d1EFB9QjJTIZCk5SKumxKY9T1FYCmJi2 N5cCMLQzI+5MgB4DT0fxeJpOhpeLYsiP2A7xrZNOCZU+8bnddltnTEqM/1WvISgjiy8S kxAK5pbao/l0EiRA/VZGkvBGBxdS1eif7BckpRIyqMKcCWwtccjkia6zxBP0lLwkGbxt HplY7Mx3CAIzJI5X0ivf21jrG6Q8MSljg4Z/z3VSUHy6aL84TCUCjPlrAj2RWPcLdh9V 8gvxiRXy5sGN7G9QE7FDAjTbRNU+LDWAWHjCrRsm365aVnrU4UFYNTTjNUb411VWRwTl Xcnw== X-Gm-Message-State: AO0yUKXp09JcRNQs9M2NJvBHdjbmbp3hLMgqioaA9mWv1KUEVNLwv/ig AyczSOA/yto/2s+oZu52TsUNlys2Ts8= X-Google-Smtp-Source: AK7set9oSzf5kH5BczSyIXnDBULTTnuRaODOR0+mACIG6kdtSGJuCRV/EhejZUcj/DTIz5dsC3aFsrMw5lQ= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a62:33c4:0:b0:592:ecb5:f51f with SMTP id z187-20020a6233c4000000b00592ecb5f51fmr846308pfz.34.1675291174649; Wed, 01 Feb 2023 14:39:34 -0800 (PST) Date: Wed, 1 Feb 2023 22:39:19 +0000 In-Reply-To: <20221212183720.4062037-1-vipinsh@google.com> Mime-Version: 1.0 References: <20221212183720.4062037-1-vipinsh@google.com> X-Mailer: git-send-email 2.39.1.456.gfc5497dd1b-goog Message-ID: <167528978572.826771.13904811225670358495.b4-ty@google.com> Subject: Re: (subset) [Patch v4 00/13] Add Hyper-v extended hypercall support in KVM From: Sean Christopherson To: Sean Christopherson , pbonzini@redhat.com, vkuznets@redhat.com, dmatlack@google.com, Vipin Sharma Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 12 Dec 2022 10:37:07 -0800, Vipin Sharma wrote: > There are two patch series combined in this one because I have rebased > my patch series (patches 8 to 13) on top of Vitaly's "Hyper-V invariant TSC control > feature" (patches 1 to 7). > https://lore.kernel.org/kvm/87o7szouyr.fsf@ovpn-194-185.brq.redhat.com/ > > Vitaly's series had some small merge conflicts on the KVM queue branch I > have fixed them in this series, no code changes. > > [...] Applied 8-11 and 13 to kvm-x86 misc. 1-7 were already merged, and I don't want to carry the sweeping TEST_ASSERT_KVM_EXIT_REASON() change, at least not in "misc", and I definitely don't want to grab it without Cc'ing the other arch maintainers. I'll follow up in that patch. [08/13] KVM: x86: hyper-v: Use common code for hypercall userspace exit https://github.com/kvm-x86/linux/commit/1a9df3262a63 [09/13] KVM: x86: hyper-v: Add extended hypercall support in Hyper-v https://github.com/kvm-x86/linux/commit/db9cf24cea69 [10/13] KVM: selftests: Test Hyper-V extended hypercall enablement https://github.com/kvm-x86/linux/commit/c4a46627e5a8 [11/13] KVM: selftests: Replace hardcoded Linux OS id with HYPERV_LINUX_OS_ID https://github.com/kvm-x86/linux/commit/f65092015a83 [13/13] KVM: selftests: Test Hyper-V extended hypercall exit to userspace https://github.com/kvm-x86/linux/commit/60325261235a -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes