From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Berger Subject: Re: [tpmdd-devel] [PATCH v4 2/2] tpm: vtpm_proxy: Implement request_locality function. Date: Tue, 16 May 2017 15:32:33 -0400 Message-ID: References: <1494460462-29022-1-git-send-email-stefanb@linux.vnet.ibm.com> <1494460462-29022-3-git-send-email-stefanb@linux.vnet.ibm.com> <484d5d9f-c769-3e38-4fe5-6dede79de717@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <484d5d9f-c769-3e38-4fe5-6dede79de717@linux.vnet.ibm.com> Sender: owner-linux-security-module@vger.kernel.org To: Ken Goldman , tpmdd-devel@lists.sourceforge.net, linux-security-module@vger.kernel.org Cc: linux-kernel@vger.kernel.org List-Id: tpmdd-devel@lists.sourceforge.net 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.