Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp2235935pxp; Fri, 18 Mar 2022 06:27:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxa8UferEgA7Yun69Kexm16uTJjTaGAJq7lIoOLJNz8ElhK8kGoI3xOw3tDooCOfFtFt5Qx X-Received: by 2002:a17:907:6283:b0:6db:aced:6698 with SMTP id nd3-20020a170907628300b006dbaced6698mr9016381ejc.283.1647610067468; Fri, 18 Mar 2022 06:27:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1647610067; cv=none; d=google.com; s=arc-20160816; b=DlgF3n+wq2RmkpIrVMCW00P1V9xvDCIQgY11jyCbWyh0qzUvFZTqhZ8/UMMnlEJgbK 7fYlXh3wwsmHMh2tDqqHYDQiG376851ibaNHM3DmPTmTtUW5PTR+3kKkPuqpr+VAC4O9 FZL8E8QUMduoxI2/MTIWzC0YAlSOUTO+yYL2QgAr5GaxxrcJWFVjYEMyXPPkBbXN1rJw XeqzgVO21o6jD9WQfhXp5z1oyQlsnruwVI5YaHDuncyisXiwnQF56nG2SmTG1Y53ZoGW xhuu9YR/fgqJrq5LAhTT7Y/MN0VR6HvmBKFp9I1KLPFwFAb1KGAAGTXtZBVPbriHqSmU V32Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from :dkim-signature; bh=awkn70QxHYniHZXut1XnxD+11rU6H5eyHpsfyTtQMCo=; b=BZh6xVBs8fXZ/Z4ghUpaIWRtZdqFEmvSEbzQ9+lh+qmUWjpQoS/hlkIHYG+FVfnHwb 6FjTceVXt8FzFjP0nfdkp4Us4pU9EDA7nwk+qm5UVoDS5rY8C7gdUnNFMf32vSo5Npmz 6y0Or76P3Ed7K3tiiMexQTqoLBazGUR0l7hpQF4RAxmm9zbCTxfqT+lKYiEM92mYAdSy iDB5nYa+l+l0U1rxLIaM/VC6Cm4Hi8VzwuVJrQ+JAzaZxuL5FXrurBYTZBdGWSLY6yyJ LF+QiYRhqt7azx/4bs7Kxwe+/W7q+fOMInEtXLwybV+sr60lrjx8Ifg2/ArWGtfHBwdq D/8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=j1bbUUsn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c26-20020a50f61a000000b00418ff09ac1csi3343779edn.292.2022.03.18.06.27.22; Fri, 18 Mar 2022 06:27:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=j1bbUUsn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233178AbiCRHpo (ORCPT + 99 others); Fri, 18 Mar 2022 03:45:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53514 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232183AbiCRHpm (ORCPT ); Fri, 18 Mar 2022 03:45:42 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C02B61F42CC; Fri, 18 Mar 2022 00:44:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647589464; x=1679125464; h=from:to:cc:subject:date:message-id; bh=WVorLasdOjXeuoPP69sky8MPUXu9hsaobNnBPkjJ6PE=; b=j1bbUUsn0MNuNmpP/NPz0yaUZMNK4xug71cDTn7We/cOXJphGtO/WYeU W7eVH/cgC9d+xXWcFMik6HYBXZcJwq/uqyLln3F3gv9WtklSWjJsJoQLQ 5q05WRHj3oH0e4Ahl8igoWs7nR7oHy4XMu+XJFRkde1Ei+T9UtzRIuVBS FWPIhEdjjr+CRddtpvdmgmun44d62H0sUVxWs25PMUfDGU8w4rkF2frua fKYerh3Kk/Cjxuz2wNUp+DCxgSbu1o7YytJKl3jdsxMhxqCOAUvSUcIdf tqar7fPUXAUmmbv6pv5kivP9KbxndPBfEMGlnG+2LL3GhtF2xurN8R5cB Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10289"; a="254641650" X-IronPort-AV: E=Sophos;i="5.90,191,1643702400"; d="scan'208";a="254641650" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Mar 2022 00:44:24 -0700 X-IronPort-AV: E=Sophos;i="5.90,191,1643702400"; d="scan'208";a="558307271" Received: from chenyi-pc.sh.intel.com ([10.239.159.73]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Mar 2022 00:44:21 -0700 From: Chenyi Qiang To: Paolo Bonzini , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Xiaoyao Li Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v5 0/3] Introduce Notify VM exit Date: Fri, 18 Mar 2022 15:49:52 +0800 Message-Id: <20220318074955.22428-1-chenyi.qiang@intel.com> X-Mailer: git-send-email 2.17.1 X-Spam-Status: No, score=-8.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Virtual machines can exploit Intel ISA characterstics to cause functional denial of service to the VMM. This series introduces a new feature named Notify VM exit, which can help mitigate such kind of attack. Patch 1: An extension of KVM_SET_VCPU_EVENTS ioctl to inject a synthesized shutdown event from user space. This is also a fix for other synthesized triple fault, e.g. the RSM patch or nested_vmx_abort(), which could get lost when exit to userspace to do migrate. Patch 2: The main patch to enable Notify VM exit. Patch 3: Add document for the new KVM capability and KVM exit reason. --- Change logs: v4 -> v5 - rename KVM_VCPUEVENTS_SHUTDOWN to KVM_VCPUEVENTS_TRIPLE_FAULT. Make it bidirection and add it to get_vcpu_events. (Sean) - v4: https://lore.kernel.org/all/20220310084001.10235-1-chenyi.qiang@intel.com/ v3 -> v4 - Change this feature to per-VM scope. (Jim) - Once VM_CONTEXT_INVALID set in exit_qualification, exit to user space notify this fatal case, especially the notify VM exit happens in L2. (Jim) - extend KVM_SET_VCPU_EVENTS to allow user space to inject a shutdown event. (Jim) - A minor code changes. - Add document for the new KVM capability. - v3: https://lore.kernel.org/lkml/20220223062412.22334-1-chenyi.qiang@intel.com/ v2 -> v3 - add a vcpu state notify_window_exits to record the number of occurence as well as a pr_warn output. (Sean) - Add the handling in nested VM to prevent L1 bypassing the restriction through launching a L2. (Sean) - Only kill L2 when L2 VM is context invalid, synthesize a EXIT_REASON_TRIPLE_FAULT to L1 (Sean) - To ease the current implementation, make module parameter notify_window read-only. (Sean) - Disable notify window exit by default. - v2: https://lore.kernel.org/lkml/20210525051204.1480610-1-tao3.xu@intel.com/ v1 -> v2 - Default set notify window to 0, less than 0 to disable. - Add more description in commit message. --- Chenyi Qiang (2): KVM: X86: Save&restore the triple fault request KVM: Add document for KVM_CAP_X86_NOTIFY_VMEXIT and KVM_EXIT_NOTIFY Tao Xu (1): KVM: VMX: Enable Notify VM exit Documentation/virt/kvm/api.rst | 45 ++++++++++++++++++++++++++++++ arch/x86/include/asm/kvm_host.h | 5 ++++ arch/x86/include/asm/vmx.h | 7 +++++ arch/x86/include/asm/vmxfeatures.h | 1 + arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/include/uapi/asm/vmx.h | 4 ++- arch/x86/kvm/vmx/capabilities.h | 6 ++++ arch/x86/kvm/vmx/nested.c | 17 ++++++++++- arch/x86/kvm/vmx/vmx.c | 44 +++++++++++++++++++++++++++-- arch/x86/kvm/x86.c | 28 +++++++++++++++++-- arch/x86/kvm/x86.h | 5 ++++ include/uapi/linux/kvm.h | 7 +++++ 12 files changed, 162 insertions(+), 8 deletions(-) -- 2.17.1