From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942068AbdAIXQl (ORCPT ); Mon, 9 Jan 2017 18:16:41 -0500 Received: from mga09.intel.com ([134.134.136.24]:40360 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750821AbdAIXQj (ORCPT ); Mon, 9 Jan 2017 18:16:39 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,341,1477983600"; d="scan'208";a="51342411" Date: Tue, 10 Jan 2017 01:16:35 +0200 From: Jarkko Sakkinen To: greg@enjellic.com Cc: Ken Goldman , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, tpmdd-devel@lists.sourceforge.net Subject: Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager Message-ID: <20170109231635.6wh25qoy7svcnys6@intel.com> References: <201701041612.v04GCfPK031525@wind.enjellic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201701041612.v04GCfPK031525@wind.enjellic.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 04, 2017 at 10:12:41AM -0600, Dr. Greg Wettstein wrote: > The kernel needs a resource manager. Everyone needs to think VERY > hard and VERY, VERY carefully about what gets put into the kernel. In > making a decision, put the ABSOLUTE smallest amount of code into the > kernel which allows various 'TPM2 personalities' to be implemented in > userspace and functionally verified and protected by the physical > instance. The emergence of commodity TEE's (SGX, et.al) should be in > the back of everyone's mind as a factor in the roadmap. Here's my cuts for the kernel: - Kernel virtualizes handle areas. It's mechanical. - Kernel does not virtualize bodies. It's not mechanical. - At least the first version of the RM will not do other than session isolation for sessions. This keeps the core for RM inside the kernel small and tight. If we start to do some weird shit to the bodies that we think is good after long hours over engineering, the implementation will be a failure. In the user space the way bodies are virtualizes is easier to fine-tune because it doesn't break every possible app using the in-kernel RM. /Jarkko