Received: by 10.223.164.202 with SMTP id h10csp2758084wrb; Sun, 12 Nov 2017 17:56:09 -0800 (PST) X-Google-Smtp-Source: AGs4zMZOjMAUZHxcxm2qxTa2BNx8blW3TSDZvAgrtMth5515aXp5kIkruayiVKJMY6dZb6ZclerU X-Received: by 10.99.117.70 with SMTP id f6mr3899067pgn.339.1510538169048; Sun, 12 Nov 2017 17:56:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510538169; cv=none; d=google.com; s=arc-20160816; b=ktQczFMAT008mULMhcViRI6v7Zf4c/KFPsR9GFdzaUetWM7E4UDzpDOjjXeWclfTka uUBKiPmDKWuQuyPTvmLDifMf5ipyMx2uiekh7dXu7k6BhMvrbSJhw1uXk7FC33P7Qpem 2kwni6PQ21myTIoSm1VUyrk4b3E+9Aa8IpIgmrJrALSoKy0am+SNq4xJRQhuOv4IAojF m5MaNmL1DQ4SQd6mYGlSEeV1yKYYWQNo2FiEdFSapy0Jd7RB6pGEcuFaNnqvJb7F7kj0 vHCw8s5uaXHAjjhDAelrB/rxCoXwPzpCvvR3UM9YOsqRUApFPA/+rCwyWQH1hnc0E6Zm T3eQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=SAQyzFCb5v6PHo49hK2hGUgUljIxmcViMJ7J8uhZVYQ=; b=BOaNGBKuOinSxQb1zr5YqGcUlOQnFzApJwU4XAZX7LYUTxokc5b5zfNY/nnFh4SwSH tjufhGwX5aAmJpS5RJ/8ZcnR10TtHlSQhxboZlMq/I+uFhw8tK16THLW2Xa/EslOrh6a t4sqNA+kdtj40QqUBl6w2VP/RG2z17O26a1WlhDh+hDdD1wmAdruREcvXIiemrYUW2u/ q/DHp/y63Wl1SHMk8RDBEGHIHbc1oeyzTUun1Lwdr9jiX7xkiPwX1wSa6qD6mySUHEmq 0rl3Dk086+qzs9cMpEpl4DX1oncaAMaDFptIyaGXyiIjsA8PKvkzoLCA43hWrkXBY12n oBNg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64si1737072pla.622.2017.11.12.17.55.56; Sun, 12 Nov 2017 17:56:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751688AbdKMBzV (ORCPT + 87 others); Sun, 12 Nov 2017 20:55:21 -0500 Received: from mga02.intel.com ([134.134.136.20]:24566 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbdKMBzU (ORCPT ); Sun, 12 Nov 2017 20:55:20 -0500 Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2017 17:55:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,386,1505804400"; d="scan'208";a="175045728" Received: from linux.intel.com ([10.54.29.200]) by fmsmga005.fm.intel.com with ESMTP; 12 Nov 2017 17:55:16 -0800 Received: from dazhang1-ssd.sh.intel.com (dazhang1-ssd.sh.intel.com [10.239.48.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 0C2ED5802CA; Sun, 12 Nov 2017 17:55:14 -0800 (PST) Date: Mon, 13 Nov 2017 18:37:59 +0800 From: Yi Zhang To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, rkrcmar@redhat.com, ravi.sahita@intel.com Subject: Re: [PATCH RFC 00/10] Intel EPT-Based Sub-page Write Protection Support. Message-ID: <20171113103758.GA29311@dazhang1-ssd.sh.intel.com> Mail-Followup-To: Paolo Bonzini , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, rkrcmar@redhat.com, ravi.sahita@intel.com References: <20171104001243.GA81548@dazhang1-ssd.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017-11-10 at 16:39:27 +0100, Paolo Bonzini wrote: > On 04/11/2017 17:54, Paolo Bonzini wrote: > > On 04/11/2017 01:12, Yi Zhang wrote: > >>> > >> Adding Ravi, > >> > >> Does anyone have further comments on current implementation, it is a > >> important feature in our next generation chip-set. > > > > What matters is not the feature, but the use case; without a use case, > > there is no point in including code for SPP in KVM. KVM doesn't use > > VMFUNC or #VE for example, because they are not necessary. > > > > SPP may become useful once we have the introspection interface. Or, if > > another hypervisor uses it, support for nested SPP may be useful (for > > example we support nested VMFUNC and should get nested #VE sooner or > > later, even though the features are not used on bare metal). > > > > Right now, however, supporting SPP does not seem to be particularly > > important honestly. > > Hi Yi Zhang, > > are you going to work on nested SPP? I guess that would be most useful > way to add SPP support to KVM (and you could also test it with > kvm-unit-tests). Hi Paolo, We Haven't planing on the nested support yet, so far there are many hardware assistance work on current SPP implemetation, and apply it in next generration icelake chip-set. Regards Yi. > > Thanks, > > Paolo From 1583694154004929077@xxx Fri Nov 10 15:40:39 +0000 2017 X-GM-THRID: 1581152810958355510 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread