[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170224181126.GC22491@obsidianresearch.com>
Date: Fri, 24 Feb 2017 11:11:26 -0700
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
tpmdd-devel@...ts.sourceforge.net,
linux-security-module@...r.kernel.org, dhowells@...hat.com,
Peter Huewe <peterhuewe@....de>,
Marcel Selhorst <tpmdd@...horst.net>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 6/7] tpm: expose spaces via a device link /dev/tpms<n>
On Fri, Feb 24, 2017 at 07:39:22PM +0200, Jarkko Sakkinen wrote:
> > I think therefore that tpmns<n> for TPM Namespace would be very
> > appropriate.
>
> Makes sense. We can go with tpmns.
When we have talked about TPM namespaces in the past it has been
around the idea of restricting which TPMs the namespace has access too
and changing the 'kernel tpm' for that namespace.
Jason
Powered by blists - more mailing lists