[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190613171141.GL1513@sasha-vm>
Date: Thu, 13 Jun 2019 13:11:41 -0400
From: Sasha Levin <sashal@...nel.org>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: peterhuewe@....de,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
jgg@...pe.ca, corbet@....net,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-doc@...r.kernel.org, linux-integrity@...r.kernel.org,
Microsoft Linux Kernel List <linux-kernel@...rosoft.com>,
Thirupathaiah Annapureddy <thiruan@...rosoft.com>,
"Bryan Kelly (CSI)" <bryankel@...rosoft.com>,
tee-dev@...ts.linaro.org
Subject: Re: [PATCH v4 1/2] fTPM: firmware TPM running in TEE
On Wed, Jun 05, 2019 at 04:39:36PM +0530, Sumit Garg wrote:
>On Wed, 5 Jun 2019 at 01:39, Sasha Levin <sashal@...nel.org> wrote:
>>
>> On Tue, Jun 04, 2019 at 11:45:52AM +0530, Sumit Garg wrote:
>> >On Thu, 30 May 2019 at 20:58, Sasha Levin <sashal@...nel.org> wrote:
>> >> + /* Open context with TEE driver */
>> >> + pvt_data->ctx = tee_client_open_context(NULL, ftpm_tee_match, NULL,
>> >> + NULL);
>> >> + if (IS_ERR(pvt_data->ctx)) {
>> >> + dev_err(dev, "%s:tee_client_open_context failed\n", __func__);
>> >
>> >Is this well tested? I see this misleading error multiple times as
>> >follows although TEE driver works pretty well.
>>
>> Yes, this was all functionally tested.
>
>Can you share your build instructions and testing approach?
Yes: it looks like you got all the kernel bits, but not the firmware.
There are instructions for it here: https://github.com/microsoft/ms-tpm-20-ref
Once it's running, you can test it by running your favorite TPM usecases
through /dev/tpm0.
--
Thanks,
Sasha
Powered by blists - more mailing lists