On Tue, Feb 09, 2016 at 11:19:15AM -0500, Stefan Berger wrote: > Jason Gunthorpe <[email protected]> wrote on 02/09/2016 12:33:23 > AM: > > > > > > On Mon, Feb 08, 2016 at 02:27:07PM -0500, Stefan Berger wrote: > > > Add the retrieval of TPM 1.2 durations and timeouts. Since this requires > > > the startup of the TPM, do this for TPM 1.2 and TPM 2. > > > > > > To not allow to interleave with commands from user space, so send the > > > TPM_Startup as the first command. The timeouts can then be gotten at any > > > later time, even interleaved with commands from user space. > > > > Do not call tpm_register until get_timeouts has completed and this > > will naturally be avoided the same way every other TPM driver does. > > Getting the timeouts cannot complete before the TPM emulator has started, > which > in turn cannot start before the ioctl returns. We don't know whether user > space > starts a client first on /dev/tpm1 or the TPM emulator starts first on the > file > descriptor. We can control which command gets *queued* for the TPM emulator > and > that's what I am doing by having the kernel queue the startup command first.
I keep saying this same solution - start a work queue just before the ioctl returns and do the get_timeouts and registration in there. Jason ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
