public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Laurent Bigonville <bigon@debian.org>,
	Alexander.Steffen@infineon.com, linux-integrity@vger.kernel.org
Subject: Re: [tpmdd-devel] tpm device not showing up in /dev anymore
Date: Fri, 17 Nov 2017 15:16:20 +0200	[thread overview]
Message-ID: <20171117131620.het4yxavz6lco6ow@linux.intel.com> (raw)
In-Reply-To: <1510672631.4078.7.camel@HansenPartnership.com>

On Tue, Nov 14, 2017 at 07:17:11AM -0800, James Bottomley wrote:
> On Tue, 2017-11-14 at 16:59 +0200, Jarkko Sakkinen wrote:
> > On Sat, Nov 11, 2017 at 01:31:32PM -0700, Jerry Snitselaar wrote:
> > > 
> > > On Sat Nov 11 17, Jason Gunthorpe wrote:
> > > > 
> > > > On Sat, Nov 11, 2017 at 12:12:57PM -0700, Jerry Snitselaar wrote:
> > > > 
> > > > > 
> > > > > Before the release_locality code would only actually release
> > > > > the locality if the request use bit was set. So after it
> > > > > grabbed the locality during probe it probably never released
> > > > > it. The idea with the new code was to release it when it was no
> > > > > longer needed so another requester would be able to take the
> > > > > tpm without having to wait for it to be released.
> > > > 
> > > > If I recall, this was so that system level things outside linux
> > > > could access the TPM properly??
> > > > 
> > > 
> > > Yes, that is what drove this initially. I believe Jarkko was also
> > > thinking of the possibility in the future where something like a vm
> > > could request a locality as well, but that is just a hazy
> > > recollection of emails from back then.
> > 
> > This was something I recall discussing in LPC 2016 in the hallway at
> > least :-) A tidbit but it could make sense to tie it to VMM, not VM.
> 
> I think we should be extremely wary of different localities before we
> have a cast iron definition of what they mean.  All the TPM PC spec
> says is that locality 4 is reserved for firmware (meaning the kernel
> should have no access) and it implies there's a privilege hierarchy,
> making 4 the most privileged and 0 the least but leaves all the
> definition to the OS.  Since we only have four other localities to play
> with, we need a global definition of what they mean in Linux (and who
> protects them) otherwise we'll get conflicting uses.  What does Windows
> use them for?
> 
> James

No idea. If I had to guess, they use only one locality for OS as this
what PTT/fTPM had when it didn't have localities. At least their
implementation works with only one locality.

/Jarkko

  reply	other threads:[~2017-11-17 13:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f9526f55-df96-64fc-a4d6-877ce04e7156@debian.org>
     [not found] ` <dcad0104c46d4d5f88e642862bdb42c2@MUCSE603.infineon.com>
     [not found]   ` <47c4300b-8701-79a6-1c58-3a5853f4c5e3@debian.org>
     [not found]     ` <595efb25-8d87-f39d-037f-9c9a98462339@debian.org>
     [not found]       ` <857106e4bb864bb8a68b1381fffc8f50@MUCSE603.infineon.com>
     [not found]         ` <20170831164015.3ajgwydgxtippwoz@rhwork>
     [not found]           ` <0d9be244-ace0-030d-6ff9-c4e94c63b7e9@debian.org>
     [not found]             ` <20170906040555.fqedhmo5277sd6fq@linux.intel.com>
2017-10-14  8:13               ` [tpmdd-devel] tpm device not showing up in /dev anymore Jerry Snitselaar
2017-10-21  8:53                 ` Laurent Bigonville
2017-10-23 13:23                   ` Jarkko Sakkinen
2017-10-23 13:45                     ` Jerry Snitselaar
2017-10-23 13:48                       ` Laurent Bigonville
2017-10-24 13:51                       ` Jarkko Sakkinen
2017-10-24 14:57                         ` Jerry Snitselaar
2017-10-24 16:07                           ` Jarkko Sakkinen
2017-11-09  0:04                             ` Laurent Bigonville
2017-11-09 19:58                               ` Laurent Bigonville
2017-11-09 23:50                                 ` Jerry Snitselaar
2017-11-10  2:19                                   ` Jerry Snitselaar
2017-11-10  0:28                                 ` Jerry Snitselaar
2017-11-10  7:07                                   ` Jerry Snitselaar
2017-11-10  8:21                                     ` Laurent Bigonville
2017-11-10 20:53                                       ` Jerry Snitselaar
2017-11-11 15:45                                         ` Jason Gunthorpe
2017-11-11 19:12                                           ` Jerry Snitselaar
2017-11-11 19:46                                             ` Jason Gunthorpe
2017-11-11 20:31                                               ` Jerry Snitselaar
2017-11-14  0:26                                                 ` Laurent Bigonville
2017-11-14  2:45                                                   ` Jason Gunthorpe
2017-11-14 14:59                                                 ` Jarkko Sakkinen
2017-11-14 15:17                                                   ` James Bottomley
2017-11-17 13:16                                                     ` Jarkko Sakkinen [this message]
2018-01-02 23:54                                                       ` Laurent Bigonville
2018-01-03  0:33                                                         ` Jerry Snitselaar
2018-01-05 19:01                                                           ` Laurent Bigonville
2018-02-09 10:53                                                           ` Laurent Bigonville
2018-02-14 11:44                                                             ` Jarkko Sakkinen
2018-03-09 17:24                                                               ` Laurent Bigonville
2018-03-15 16:24                                                                 ` Jarkko Sakkinen
2018-05-03 11:38                                                                   ` Laurent Bigonville
2018-05-03 17:43                                                                     ` Jerry Snitselaar
2018-05-04  8:20                                                                       ` Jarkko Sakkinen
2018-05-04  8:18                                                                     ` Jarkko Sakkinen
2018-05-04 14:22                                                                       ` Jerry Snitselaar
2017-11-14 14:55                                               ` Jarkko Sakkinen
2017-11-14 14:43                                         ` Jarkko Sakkinen
2017-10-25  8:04                         ` Laurent Bigonville

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171117131620.het4yxavz6lco6ow@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bigon@debian.org \
    --cc=jgg@ziepe.ca \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox