From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2E2EC43441 for ; Tue, 20 Nov 2018 10:58:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 867E620685 for ; Tue, 20 Nov 2018 10:58:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 867E620685 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-sgx-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728672AbeKTV0y (ORCPT ); Tue, 20 Nov 2018 16:26:54 -0500 Received: from mga03.intel.com ([134.134.136.65]:2200 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728437AbeKTV0y (ORCPT ); Tue, 20 Nov 2018 16:26:54 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Nov 2018 02:58:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,256,1539673200"; d="scan'208";a="281477467" Received: from jsakkine-mobl1.tm.intel.com (HELO localhost) ([10.237.50.177]) by fmsmga005.fm.intel.com with ESMTP; 20 Nov 2018 02:58:17 -0800 Date: Tue, 20 Nov 2018 12:58:17 +0200 From: Jarkko Sakkinen To: Jethro Beekman Cc: "x86@kernel.org" , "platform-driver-x86@vger.kernel.org" , "linux-sgx@vger.kernel.org" , "dave.hansen@intel.com" , "sean.j.christopherson@intel.com" , "nhorman@redhat.com" , "npmccallum@redhat.com" , "serge.ayoun@intel.com" , "shay.katz-zamir@intel.com" , "haitao.huang@linux.intel.com" , "andriy.shevchenko@linux.intel.com" , "tglx@linutronix.de" , "kai.svahn@intel.com" , "mark.shanahan@intel.com" Subject: Re: [PATCH v17 18/23] platform/x86: Intel SGX driver Message-ID: <20181120105817.GA14594@linux.intel.com> References: <20181116010412.23967-1-jarkko.sakkinen@linux.intel.com> <20181116010412.23967-19-jarkko.sakkinen@linux.intel.com> <20181119150655.GA11843@linux.intel.com> <20181119171934.GA16252@linux.intel.com> <63b97d22-9d28-e0f8-492d-27e5cc456fce@fortanix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <63b97d22-9d28-e0f8-492d-27e5cc456fce@fortanix.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-sgx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-sgx@vger.kernel.org On Mon, Nov 19, 2018 at 05:39:04PM +0000, Jethro Beekman wrote: > Let's keep it as separated as possible for now until KVM lands and we get > the module capability back, instead of integrating everything so tightly > Jethro Beekman | Fortanix We can keep the driver structure and still move it under arch/x86/kernel/cpu. When landing the KVM code we can then allow the driver part to be compiled as module. It is not the only LKM under arch/x86. Would also simplify both way we develop SGX code alot, not least because there would be clear consumer of the pull requests. /Jarkko