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 CB7C7C83F22 for ; Wed, 30 Aug 2023 00:07:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241393AbjH3AHH (ORCPT ); Tue, 29 Aug 2023 20:07:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34602 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241388AbjH3AGy (ORCPT ); Tue, 29 Aug 2023 20:06:54 -0400 Received: from mail-yw1-x114a.google.com (mail-yw1-x114a.google.com [IPv6:2607:f8b0:4864:20::114a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E7651BB for ; Tue, 29 Aug 2023 17:06:52 -0700 (PDT) Received: by mail-yw1-x114a.google.com with SMTP id 00721157ae682-58d799aa369so70282207b3.0 for ; Tue, 29 Aug 2023 17:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1693354011; x=1693958811; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:from:to:cc:subject:date:message-id:reply-to; bh=5vQWDWN9QjQwmRYIzABg1CIzIVHW8NaLWdBZKl8U/Q4=; b=AZuTU6WWYG/1eKsiMfDEMZ3N8v1aLWh7GKlSx4AFwdgj1D7xzsDPHZdnLHHO3TxCZ6 gFqTVarp8VBZRsnr2fz2ITi7nmuHLt0ZUjq/NZHqNfgy8TU4lBqIXMwsAhLkrXBZ+7VF vQqAc3S+x/uNEh6GcjzID4nzeE+UgCSkcoH64T8UerD7GWxiA0Im9agbziI/+HeoxA5m fxit4XtCuVnb8DljWAytymTM4BHHdiJBj0kNfb1aO8VbpoANjfdbxAG3s99zP2ckA7J9 nxKM75nYS4LXblEzmDMTgkZWnjkrlyAooihwsv88VewBocQB54/cKdv+gZzquHgIxZ08 FKfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693354011; x=1693958811; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5vQWDWN9QjQwmRYIzABg1CIzIVHW8NaLWdBZKl8U/Q4=; b=AC7kJPmS+Go02RXFJh/wp5rOcFk2R40Uj5wrLGw4lQmHCZY74c2n7n3DpOQLLdXKgS +qMGg1Q9g42H0cAKMYJPi0UVgse88u5vr0w8bRarcu9yM4xEchVjqU2WjG+ddMD5+PBB lm9joJADk8sP17NK4waDsMsW4cSQfVtJ7iwrE0zAA+adjf3m9lYeDbLv2IjIaGRE0/T0 kyBvFlPca8T7sxLbds1WMo95C8sA6mv1w5U24DcACTpJnpzymWaYMIE0d4BKvyEmxsUj TEsmiOut6nnhj3R70qo/5Lm9proC9NmHvHyv0TFpCAke/JZcUCSa+1UJvgJ/9Tx1O1ZU Sowg== X-Gm-Message-State: AOJu0Yxepk7EyujtsWuMEJBWCzojaZs3rX0MFRKgP7nc1Y0xfwHqehCw NO3rViXDMeQGlGeKHGO1aTBkVSsR5tg= X-Google-Smtp-Source: AGHT+IHGR1128vmCMWLmYqOJ14jKzl9S/74xwIXVowUidZGNH6Z3+8/9wDX5R9FytvDrzfDNrwCx8e8zG/U= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a81:b3ca:0:b0:589:a5c6:4a8e with SMTP id r193-20020a81b3ca000000b00589a5c64a8emr16313ywh.1.1693354011726; Tue, 29 Aug 2023 17:06:51 -0700 (PDT) Reply-To: Sean Christopherson Date: Tue, 29 Aug 2023 17:06:33 -0700 In-Reply-To: <20230830000633.3158416-1-seanjc@google.com> Mime-Version: 1.0 References: <20230830000633.3158416-1-seanjc@google.com> X-Mailer: git-send-email 2.42.0.rc2.253.gd59a3bf2b4-goog Message-ID: <20230830000633.3158416-8-seanjc@google.com> Subject: [GIT PULL] KVM: x86: VMX changes for 6.6 From: Sean Christopherson To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Sean Christopherson Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org VMX changes for 6.6. Nothing mindblowing, by far the most interesting change is the super late fix for NMI VM-Exits that you've already looked at. The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c: Linux 6.5-rc2 (2023-07-16 15:10:37 -0700) are available in the Git repository at: https://github.com/kvm-x86/linux.git tags/kvm-x86-vmx-6.6 for you to fetch changes up to 50011c2a245792993f2756e5b5b571512bfa409e: KVM: VMX: Refresh available regs and IDT vectoring info before NMI handling (2023-08-28 20:07:43 -0700) ---------------------------------------------------------------- KVM: x86: VMX changes for 6.6: - Misc cleanups - Fix a bug where KVM reads a stale vmcs.IDT_VECTORING_INFO_FIELD when trying to handle NMI VM-Exits ---------------------------------------------------------------- Sean Christopherson (3): KVM: VMX: Drop manual TLB flush when migrating vmcs.APIC_ACCESS_ADDR KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set KVM: VMX: Refresh available regs and IDT vectoring info before NMI handling Shiyuan Gao (1): KVM: VMX: Rename vmx_get_max_tdp_level() to vmx_get_max_ept_level() arch/x86/kvm/vmx/vmx.c | 38 +++++++++++++++++--------------------- 1 file changed, 17 insertions(+), 21 deletions(-)