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 X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 695EAC3F68F for ; Thu, 12 Dec 2019 18:07:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 47D41227BF for ; Thu, 12 Dec 2019 18:07:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=oracle.com header.i=@oracle.com header.b="QoHqsVEg" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730284AbfLLSHO (ORCPT ); Thu, 12 Dec 2019 13:07:14 -0500 Received: from aserp2120.oracle.com ([141.146.126.78]:49638 "EHLO aserp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730082AbfLLSHO (ORCPT ); Thu, 12 Dec 2019 13:07:14 -0500 Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xBCHn5xg022218; Thu, 12 Dec 2019 18:04:32 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2019-08-05; bh=6nE9TIG7gNozX0c5JrZbeLjKkq4aQbbrTaX/7iiac6M=; b=QoHqsVEgjltKrKrKhFjzmk9Zn/ASebnNcXuELwwEQ/5cS9mmVSmps2rX7hNKBuX6pXMT sdm52YxuW5sfixN5za1MBMEg4vDiUE7Ym7hbqI5IRT43WbebTKsJ9n0AxIBczDbozi9o 25fjX4Es42jQ+8e+O/zXdxDvS78UjmxyO0C9iMChc/hEBLLSXsOUyQlwpdvQcjjTNDLu BmMHZPmMADobfwXrXMVsBhCx9Wmch2cHttWSr4ZuY50Y3L+3Xkh7gwQrC/nRPzeQEBZ0 OylEEo/4AeVjb9eIjVz/2atdPhT3gHhIU63AWXR+laKZYf27RZgzk0Fzi3vuOfQLYdZ0 uA== Received: from aserp3020.oracle.com (aserp3020.oracle.com [141.146.126.70]) by aserp2120.oracle.com with ESMTP id 2wr41qmpbp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 12 Dec 2019 18:04:32 +0000 Received: from pps.filterd (aserp3020.oracle.com [127.0.0.1]) by aserp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xBCHnNUj192570; Thu, 12 Dec 2019 18:04:32 GMT Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserp3020.oracle.com with ESMTP id 2wumw0r9f8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 12 Dec 2019 18:04:32 +0000 Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id xBCI4SXO006421; Thu, 12 Dec 2019 18:04:28 GMT Received: from [192.168.14.112] (/109.65.223.49) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 12 Dec 2019 10:04:27 -0800 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: [PATCH v4 11/19] x86/cpu: Print VMX flags in /proc/cpuinfo using VMX_FEATURES_* From: Liran Alon In-Reply-To: Date: Thu, 12 Dec 2019 20:04:19 +0200 Cc: Paolo Bonzini , Sean Christopherson , Borislav Petkov , Thomas Gleixner , Ingo Molnar , the arch/x86 maintainers , "H. Peter Anvin" , Peter Zijlstra , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , =?utf-8?B?UmFkaW0gS3LEjW3DocWZ?= , Vitaly Kuznetsov , Wanpeng Li , Joerg Roedel , Tony Luck , Tony W Wang-oc , Len Brown , Shuah Khan , LKML , kvm list , linux-edac@vger.kernel.org, Linux PM list , "open list:KERNEL SELFTEST FRAMEWORK" , Jarkko Sakkinen Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191128014016.4389-1-sean.j.christopherson@intel.com> <20191128014016.4389-12-sean.j.christopherson@intel.com> <20191212122646.GE4991@zn.tnic> <4A24DE75-4E68-4EC6-B3F3-4ACB0EE82BF0@oracle.com> <17c6569e-d0af-539c-6d63-f4c07367d8d1@redhat.com> <20191212174357.GE3163@linux.intel.com> <52dd758d-a590-52a6-4248-22d6852b75cd@redhat.com> To: Jim Mattson X-Mailer: Apple Mail (2.3445.4.7) X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9469 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=869 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1912120140 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9469 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=926 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1912120140 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org > On 12 Dec 2019, at 19:57, Jim Mattson wrote: >=20 > On Thu, Dec 12, 2019 at 9:53 AM Liran Alon = wrote: >=20 >> Why should CPU VMX features be treated differently than standard = CPUID deduced features? >=20 > Do we have the right Intel people on the recipient list to answer this > question? Presumably, Intel felt that this information should be > available in supervisor mode only. >=20 > Sean? Good question. Probably because it just makes sense that Ring3 will = never need to use this info as all VMX instructions are privileged. i.e. Can only be = executed in Ring0. De-facto in KVM we have discovered this assumption to be problematic = BTW, as KVM created an interface to query VMX MSRs values to properly define = the requested vCPU model. :P (See kvm_get_msr_feature())