From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Ken Goldman <kgold@linux.vnet.ibm.com>,
tpmdd-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH v4 2/2] tpm: vtpm_proxy: Implement request_locality function.
Date: Tue, 16 May 2017 15:32:33 -0400 [thread overview]
Message-ID: <aa84ca0a-f976-bf22-9cfd-40405c8f3ef8@linux.vnet.ibm.com> (raw)
In-Reply-To: <484d5d9f-c769-3e38-4fe5-6dede79de717@linux.vnet.ibm.com>
On 05/16/2017 03:03 PM, Ken Goldman wrote:
> On 5/10/2017 7:54 PM, Stefan Berger wrote:
>> Implement the request_locality function. To set the locality on the
>> backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
>> a command to the backend to set the locality for the next commands.
>
> When this says "for the next commands", does that mean that the locality
> is fixed for all commands until a new request_locality is sent to
> change it?
Yes.
prev parent reply other threads:[~2017-05-16 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 23:54 [PATCH v4 0/2] Extend the vTPM proxy driver to pass locality Stefan Berger
2017-05-10 23:54 ` [PATCH v4 1/2] tpm: Refactor tpm_transmit pulling out tpm_transfer function Stefan Berger
2017-05-12 13:30 ` Stefan Berger
2017-05-15 12:40 ` Jarkko Sakkinen
2017-05-15 16:04 ` Stefan Berger
2017-05-15 16:06 ` Stefan Berger
[not found] ` <1494460462-29022-1-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-10 23:54 ` [PATCH v4 2/2] tpm: vtpm_proxy: Implement request_locality function Stefan Berger
2017-05-15 12:41 ` Jarkko Sakkinen
2017-05-15 15:56 ` Stefan Berger
2017-05-20 12:47 ` Jarkko Sakkinen
2017-05-21 23:52 ` Stefan Berger
2017-05-24 19:25 ` Jarkko Sakkinen
2017-05-16 19:03 ` [tpmdd-devel] " Ken Goldman
2017-05-16 19:32 ` Stefan Berger [this message]
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=aa84ca0a-f976-bf22-9cfd-40405c8f3ef8@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=kgold@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).