From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423284AbdKQXfx (ORCPT ); Fri, 17 Nov 2017 18:35:53 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:53117 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161034AbdKQXfq (ORCPT ); Fri, 17 Nov 2017 18:35:46 -0500 Date: Sat, 18 Nov 2017 00:34:33 +0100 (CET) From: Thomas Gleixner To: Darren Hart cc: Jarkko Sakkinen , platform-driver-x86@vger.kernel.org, LKML , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-doc@vger.kernel.org, Jonathan Corbet Subject: Re: [PATCH v5 11/11] intel_sgx: driver documentation In-Reply-To: <20171117214310.GB25974@fury> Message-ID: References: <20171113194528.28557-1-jarkko.sakkinen@linux.intel.com> <20171113194528.28557-12-jarkko.sakkinen@linux.intel.com> <20171117214310.GB25974@fury> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-1680850187-1510961564=:2186" Content-ID: X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1680850187-1510961564=:2186 Content-Type: text/plain; CHARSET=ISO-8859-15 Content-Transfer-Encoding: 8BIT Content-ID: On Fri, 17 Nov 2017, Darren Hart wrote: @intel: I removed intel-sgx-kernel-dev@lists.01.org from CC because I can do without the silly moderation spam of that list. Please disable that nonsense. > On Mon, Nov 13, 2017 at 09:45:28PM +0200, Jarkko Sakkinen wrote: > Is SGX considered architectural or not? A quick search of the SDM > includes it in Volume 3: > > Volume 3: Includes the full system programming guide, parts 1, 2, 3, and > 4. Describes the operating-system support environment of Intel® 64 and > IA-32 architectures, including: memory management, protection, task > management, interrupt and exception handling, multi-processor support, > thermal and power management features, debugging, performance > monitoring, system management mode, virtual machine extensions (VMX) > instructions, Intel® Virtualization Technology (Intel® VT), and Intel® > Software Guard Extensions (Intel® SGX). > > https://software.intel.com/en-us/articles/intel-sdm > > Depending on the answer, this impacts whether this belongs in > drivers/platform/x86 or arch/x86/platform per our recent agreement with > Thomas. > > Thomas, Mingo, HPA, do you wish to see this organized/located > differently than it is here in v5? This is architecural. From the cursory read of that series it seems there are two parts to it: 1) The actual core handling, which should be in arch/x86 because that hardly qualifies as a 'platform' device driver. 2) The user space interface, which can be separated out perhaps. I don't know how intertwingled they are, but that's hard to tell from the actual patches w/o doing a deep inspection. Jarkko should be able to answer that. Thanks, tglx --8323329-1680850187-1510961564=:2186--