Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp3663877imm; Mon, 25 Jun 2018 02:29:05 -0700 (PDT) X-Google-Smtp-Source: ADUXVKK5WalSHVVtBuFo4AlgIzz82sEdo9/8tl6KIbHA2GUf28yvgtBkJnXHY3qqBwHm7Q86uPmE X-Received: by 2002:a62:e70e:: with SMTP id s14-v6mr12295155pfh.131.1529918945834; Mon, 25 Jun 2018 02:29:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529918945; cv=none; d=google.com; s=arc-20160816; b=rOiLsWow07bdlgrFlJV3ANUxHQpgrCVd5h/WmJNgBI+CNsuch356H1WdT6lkLByE96 sLS/QDQbpiyp1Fc66bEWbf533hI8p80ZxlPUQ2aiO3fhioq9iovaE0uq7FdPAgYRufO0 FkcwbmTyDeiCUBisJ6XBo877y/fj+ySf2BPkbXLu7TgSennNL4skRfP/PRVZIEpnlJtt QYvicViYiL9ul3xlUSO27STUhfLpEkPrr7aSqIS9OQX0AXIpMLUrd98MeYMXltDVLkHj 74DYqJNy9uU6tEUke2+IO0BDKIn86FYF1/VxQahXRtODhQzA4yKnJ0XzDs91dPkW8koi 3Htw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:date:cc:to:from:subject :message-id:arc-authentication-results; bh=DFo0WCtnp/dW07ZLhR59Zw6ZIHfiVWlryp8rbJnx4II=; b=Htby3CajEli/3rNNk+MiwF/UJd2sIuVFAFb+0lbvJEjhrD+u4bc8P/c6Ctb4KqJZDa uvonam5KChUwc5J/79+0o9brinrQaA6iJ6CctZAPME2tj4MQ7b8YJMOHIVWtmib6vhgT pP9UADoj7Go44Pa0nZSPwopOW056D5+oOP4X8h+nFarOWRULZhonN/bZ6Qoh6H2nhD1c us07vDOx9QCtA+nqcB7CeeNBwmSmMlE3VpN53N2AvEdWiiH8rGOsLgZr6u1Ns8lgE6jN S7AgxT9QHj3cwVKH/2FW+ePFgNksq5SSjirKXUZIOJaxZewZV78HbMEYZwGSvWBUC/zc E07w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 67-v6si3851111pgi.456.2018.06.25.02.28.51; Mon, 25 Jun 2018 02:29:05 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754998AbeFYJ2A (ORCPT + 99 others); Mon, 25 Jun 2018 05:28:00 -0400 Received: from mga18.intel.com ([134.134.136.126]:48244 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754253AbeFYJ15 (ORCPT ); Mon, 25 Jun 2018 05:27:57 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jun 2018 02:27:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,269,1526367600"; d="scan'208";a="210902501" Received: from jsakkine-mobl1.tm.intel.com (HELO sfriis-mobl.ger.corp.intel.com) ([10.237.50.42]) by orsmga004.jf.intel.com with ESMTP; 25 Jun 2018 02:27:53 -0700 Message-ID: Subject: Re: [intel-sgx-kernel-dev] [PATCH v11 13/13] intel_sgx: in-kernel launch enclave From: Jarkko Sakkinen To: Nathaniel McCallum , luto@kernel.org Cc: Neil Horman , x86@kernel.org, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, intel-sgx-kernel-dev@lists.01.org, hpa@zytor.com, dvhart@infradead.org, tglx@linutronix.de, andy@infradead.org, Peter Jones Date: Mon, 25 Jun 2018 12:27:53 +0300 In-Reply-To: References: <20180608171216.26521-1-jarkko.sakkinen@linux.intel.com> <20180608171216.26521-14-jarkko.sakkinen@linux.intel.com> <20180611115255.GC22164@hmswarspite.think-freely.org> <20180612174535.GE19168@hmswarspite.think-freely.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1-2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-06-20 at 12:28 -0400, Nathaniel McCallum wrote: > As I understand it, the current policy models under discussion look like this: > > 1. SGX w/o FLC (not being merged) looks like this: > Intel CPU => (Intel signed) launch enclave => enclaves > > 2. SGX w/ FLC, looks like this: > Intel CPU => kernel => launch enclave => enclaves > > 3. Andy is proposing this: > Intel CPU => kernel => enclaves What if MSRs are not writable after hand over to the OS? It is a legit configuration at least according to the SDM. /Jarkko