From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751953AbdKULMi (ORCPT ); Tue, 21 Nov 2017 06:12:38 -0500 Received: from mail.skyhub.de ([5.9.137.197]:34958 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751772AbdKULMg (ORCPT ); Tue, 21 Nov 2017 06:12:36 -0500 Date: Tue, 21 Nov 2017 12:10:09 +0100 From: Borislav Petkov To: Jarkko Sakkinen Cc: intel-sgx-kernel-dev@lists.01.org, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 11/11] intel_sgx: driver documentation Message-ID: <20171121111009.d6h2pqhmlqkf7yby@pd.tnic> References: <20171113194528.28557-1-jarkko.sakkinen@linux.intel.com> <20171113194528.28557-12-jarkko.sakkinen@linux.intel.com> <20171114083647.uxlaov56s2xw3pua@pd.tnic> <20171114204948.f6g2m62kx5gr5xtw@linux.intel.com> <20171114215327.qiqze33uvhlu555g@pd.tnic> <20171120223741.52dj6gevcwn5jzag@linux.intel.com> <20171120224256.kz3qvz4ek6ky7ywc@pd.tnic> <20171120234145.6bnm5s5ntevbzjfk@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20171120234145.6bnm5s5ntevbzjfk@linux.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 21, 2017 at 01:41:45AM +0200, Jarkko Sakkinen wrote: > In potential deployments of SGX, the owner could do this either in the > firmware level or OS level depending whether the MSRs are configured as > writable in the feature control. > > One option would be to have a config flag to decide whether to require > MSRs to be writable or not. "potential", "would", "could" - all carefully formulated. :-) Realistically, though, I'm afraid OEMs would jump on the opportunity to control yet another arch aspect like wasps on honey. So having a way to override what the firmware decided for me - without even asking me - would be RealGood(tm). -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.