Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3937720pxk; Tue, 22 Sep 2020 06:36:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzA0QdTpx7+HWbAL16TGbRoTAN9gpVJCKGAew7gkQpKVktLWlWpIWGFwoCYqYk9G+ZA5F+x X-Received: by 2002:a17:906:3495:: with SMTP id g21mr4814668ejb.121.1600781815533; Tue, 22 Sep 2020 06:36:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600781815; cv=none; d=google.com; s=arc-20160816; b=hOcpNt41Z1VVL2LiFTPJk4xbgmad5csGcZSXLN7UU4YdxoLfWB6HDQMDTqRRynQnQa qyGXID19McGYc1EmxDFr6u/LIWX5FXnNuUdEKJ4gOvbfBp/sx8M8lSs1QgtYjlaV/Nmb iCQedVJSZAfHRtK0RlKvJQMTbJElhI1SC3IeALFg8PDuFfMXQjYI3a51QGpy8Ci8L9CV xK2kFDByVMgvQLbC9aV2e+n7CAU7YCXy5h5N56uzO90zbMg1dvIDblI+pirlS0mIDCua vDzVK+EB6Lpl/R15d20x8ikarWCCPAmG0m0qVC1whdw1KmyD5YfHHJ9agvFk6sMF5CSw pIrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=933GUut1+TrG+98/jn2IqlWr/ZWUBB9JCfd+Na9nkPQ=; b=pyvwZTHC3CPdHDWyN9Tl9+9iZrsYTGWeuHZndXzPmVkPjqtF7QVFQXXDnHFlz79ZIg YjvOaU2IdQAesnH+wesTRi1R3qT+5JorD3DIPME0QnyQurEusYEC/mM4U/c7xyZqJNj4 N9gIlh5MO82zbE+uy7nmpWd/QLj0B9JfIm3g3lwMNpaGhUVsa96nMhe8C1332E1sBAWz zhjFLW7kYSep4xJexQ3Inm4cb1c959E3lnRUKtxhWrEIDkSXtU+iYXYm2ERpQpbNuyNB Q7cMekCELE5ZTxHS47S3p4J6C1iW5xFh3eO2zDNAjeMWjtcYNsbpoHKsEG7Vxw5DiPFa k7sw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Vnq1wil1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a18si10175864edy.407.2020.09.22.06.36.32; Tue, 22 Sep 2020 06:36:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Vnq1wil1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726655AbgIVNdH (ORCPT + 99 others); Tue, 22 Sep 2020 09:33:07 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:20508 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726578AbgIVNdG (ORCPT ); Tue, 22 Sep 2020 09:33:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600781585; 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=933GUut1+TrG+98/jn2IqlWr/ZWUBB9JCfd+Na9nkPQ=; b=Vnq1wil1moEQqWUuxL9nxz13RRWWKqbVZUASp3gmYoTe1IjCK3V8/LadW2n5Gj+S/U44TR PrbZ2zREcFqrJWNfFeXPpjAp0BxI8Lk/GbWFk9rx6JNmhVY5l9/oP95sTIgSgfb/yvGPsV T3cFN2OPxcPrSZ/nAOtxHC2fmrJF0SE= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-528-fHshEE5HNIuS-M2D254a-w-1; Tue, 22 Sep 2020 09:33:01 -0400 X-MC-Unique: fHshEE5HNIuS-M2D254a-w-1 Received: by mail-wm1-f72.google.com with SMTP id y18so584894wma.4 for ; Tue, 22 Sep 2020 06:33:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=933GUut1+TrG+98/jn2IqlWr/ZWUBB9JCfd+Na9nkPQ=; b=oAMtrir99+s5AJtPGjAm0aWNnEd+tluxU6iWtg1RMRpexUEi+3QT8okeLgLJt3xoac gdY3Op5PlL7LlP+NyeliNpUt35jaIMHGNdotZB/WM4yyFc2Q7j9AOtuJA/6ZV0D/l0Q+ +cBG6l+32TC1urHfUnFGEmzE4EEELQXj7PajiFryn9ul5LMpyqrTCJOIjZhUMe2oet2J AeJdKjQXgJWPplgveyl9Sf7z8n4siBPQqfeFFBS8cVVFiBoceTuiZZP2Az4/3f+kY+Hr Yw/NkRVblBFGq/EUkkPy5Mk2N4WQDyUaIPmCcJhbSuARA8iBLQ62NQya9mywJKaFY+n+ TCmw== X-Gm-Message-State: AOAM533U/LPAdHZX+i1eAxDB++F/4Ce+403NTGMpWdgXj56QJ/upRWsD kUqmwEXS4mMq1j27rOP53dqvg4ySwxNuqv28PaajdJbql34hLbBSXSunZnamCr6IW3T3o0HeKBa i/nq5/3UFqQ9ebiIMuuCqAR7T X-Received: by 2002:a5d:5106:: with SMTP id s6mr5808351wrt.166.1600781580059; Tue, 22 Sep 2020 06:33:00 -0700 (PDT) X-Received: by 2002:a5d:5106:: with SMTP id s6mr5808331wrt.166.1600781579824; Tue, 22 Sep 2020 06:32:59 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:ec2c:90a9:1236:ebc6? ([2001:b07:6468:f312:ec2c:90a9:1236:ebc6]) by smtp.gmail.com with ESMTPSA id p9sm4444362wma.42.2020.09.22.06.32.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Sep 2020 06:32:59 -0700 (PDT) Subject: Re: [PATCH] KVM: x86: Add kvm_x86_ops hook to short circuit emulation To: Sean Christopherson , Wanpeng Li Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm , LKML , Tom Lendacky References: <20200915232702.15945-1-sean.j.christopherson@intel.com> <20200916173416.GF10227@sjchrist-ice> From: Paolo Bonzini Message-ID: <2cacbe0d-703b-cb06-ac5b-96841f145b95@redhat.com> Date: Tue, 22 Sep 2020 15:32:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20200916173416.GF10227@sjchrist-ice> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16/09/20 19:34, Sean Christopherson wrote: > > The intent of posting the patch standalone is so that SGX, SEV-ES, and/or TDX > have "ready to go" support in upstream, i.e. can change only the VMX/SVM > implementation of is_emulated(). I'm a-ok dropping the handle_ud() change, > or even the whole patch, until one of the above three is actually ready for > inclusion. I think it's fine with the "can" in the name. Hopefully one of the three will go in soon... Paolo