Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp323899ybm; Tue, 26 May 2020 18:15:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZblUTKARXpNYzhMpzsA1IPLWvDJl2bHZ1ZWqsr0PVPyh060dDe2zHSQDv+qVkNuBwBZmx X-Received: by 2002:a50:ec0d:: with SMTP id g13mr22040561edr.296.1590542136355; Tue, 26 May 2020 18:15:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590542136; cv=none; d=google.com; s=arc-20160816; b=WSoYuw0GvoIJOp8FNBEQHS4X7BdmZmkoztIDSVEekhR65y/eJZ79ui5Py0+I6KLBA5 +blZyQuoZavok1+grKYP6vJqertUYaneloFTaQbe7QbpkzZbpdk64e48IajfMVfLyADL JnF+ObJ46Bg0SrfANHtLEvb8MuNxGKUDatAQcnh2Zig79V3055rk2x0FkRoam42OrGs9 quvetzbmzy2ylrDp0c1Sh6LFqhwiRcrcyrkR37NNGfi606Tr4tSfk9TiuQvkQtzHTBC+ Qy6CD5GHAPzXwZyfUhUkFVJ7SpCA9yopjPSPTxrLa12kg+/n1/v2PDMTe2+9E0szcF7Q bMTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=6sd5NaYGl7My6f3quo9defR+sQQ9lKLSTnzcmXfRx6E=; b=La8N3L0cYdslp/cisMy3UZ18bnS9BRTlDFSaYuIYTke0gq5fiW+gmIrzw2wtPsCnQs iVZ3oGylHPZhBwxo76FnYRJU+HRONRKkOiOtQ6ElIq3XuuuZGvdfDakTsnIk139F3LYa PD9yExUZWKqSJTPiAS0ecGgtFdbme1MXT569N5+HXGl+MCYTi67FSDOarmLVqXdlTUSl qW74+Hg/b/sMBdt6AHajgiJyZHzQBh4mB5qtrIkrNXayEkOwf0N4E5pSo7BfnZBWGKjp UOS33ULSqX7bRXGsbAi6/ry3BXvtFnIElBiHZczHW660Xy42IKCYCmr887w2n/JhHdiH m/CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Kkne23X7; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z4si829202edx.431.2020.05.26.18.15.13; Tue, 26 May 2020 18:15:36 -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=@kernel.org header.s=default header.b=Kkne23X7; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404562AbgEZWvX (ORCPT + 99 others); Tue, 26 May 2020 18:51:23 -0400 Received: from mail.kernel.org ([198.145.29.99]:59174 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404557AbgEZWvV (ORCPT ); Tue, 26 May 2020 18:51:21 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1A8E82075F; Tue, 26 May 2020 22:51:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590533481; bh=Iwnq+0PLVIW/wTxxSSJYZn9hBX0RhzrKVgiIaqvXdfU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Kkne23X7TYidyChop6jl4HJ/ZaMCUsL0eWZd64FhOjF3Dq2q+3h6oo3uB+7cs7j0Z 8/hZvshsLWwMkPOSG1RBW7cY3PIIVQtJXbcNnMtXXv9mSHznFUiBDL8FY7HelCQbId 44b/CwtAsYtFyjiHBw2r+vFL68b+04mQQ2DLKslU= Date: Tue, 26 May 2020 18:51:20 -0400 From: Sasha Levin To: Don Porter Cc: Thomas Gleixner , Jarkko Sakkinen , Andi Kleen , linux-kernel@vger.kernel.org, bp@alien8.de, luto@kernel.org, hpa@zytor.com, dave.hansen@intel.com, tony.luck@intel.com, ravi.v.shankar@intel.com, chang.seok.bae@intel.com Subject: Re: [PATCH v12 00/18] Enable FSGSBASE instructions Message-ID: <20200526225120.GH33628@sasha-vm> References: <20200518153407.GA499505@tassilo.jf.intel.com> <371e6a92cad25cbe7a8489785efa7d3457ecef3b.camel@linux.intel.com> <87v9ksvoaq.fsf@nanos.tec.linutronix.de> <20200519164853.GA19706@linux.intel.com> <7eb45e02-03bf-0af0-c915-794bf49d66d7@cs.unc.edu> <87h7w7qy18.fsf@nanos.tec.linutronix.de> <20200526202739.GG33628@sasha-vm> <7a25e82a-9ef1-f13b-be42-2d7a693592b4@cs.unc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7a25e82a-9ef1-f13b-be42-2d7a693592b4@cs.unc.edu> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 26, 2020 at 06:03:35PM -0400, Don Porter wrote: >On 5/26/20 4:27 PM, Sasha Levin wrote: >>I'm really worried about the disconnect between how you view the current >>state of Graphene (and the industry) vs Intel and the various cloud >>providers. >> >>You keep suggesting that its just past the academic research state, >>while Intel and the big cloud providers are already pushing it to >>external customers.? Every one of those cloud providers has a preview/GA >>secure enclave offering. >> > >I wonder if you are conflating Graphene with SGX? I understand that >many cloud vendors are offering SGX in preview/GA, but there are other >frameworks to build these offerings on, such as Intel's SGX SDK or >Haven. It would be news to me if every major cloud vendor were >putting Graphene in production. Sorry, I wasn't trying to suggest that all cloud vendors are pushing Graphene, but rather than SGX enabled platforms became a commodity product, users will end up using Graphene-like applications. Let me provide an example: https://www.alibabacloud.com/blog/protecting-go-language-applications-with-the-graphene-library-os-on-intel%C2%AE-sgx%C2%AE-secured-alibaba-cloud_594889 - a "practical" guide on how to run Graphene in production environment on one of the big cloud vendor platforms. -- Thanks, Sasha