[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <7ec8265f-265d-641a-6da3-d931f8df4819@linux.vnet.ibm.com>
Date: Fri, 11 Aug 2017 17:42:43 -0400
From: Ken Goldman <kgold@...ux.vnet.ibm.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-ima-devel@...ts.sourceforge.net,
linux-security-module@...r.kernel.org,
tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [Linux-ima-devel] [tpmdd-devel] [PATCH] tpm: improve tpm_tis
send() performance by ignoring burstcount
Following up on this thread based on this week's TCG call ...
1 - burstCount can safely be ignored on writes. This is explicit in
most places in the TCG spec. In places where it is not explicit, it was
simply an editorial omission. We are going through the spec and adding
"without incurring wait states."
TCG is willing to publish an errata if that makes developers more
comfortable.
2 - These are multi-mhz buses. The TPM vendors conformed that wait
states, even if incurred, will be sub-usec. I.e., less that a microsecond.
Essentially, the DD is loading the FIFO, and the TPM is unloading the
FIFO at processor speeds.
Thus, even if one were worried about an odd system new enough to have a
TPM, but old enough to have an LPC attached printer, keyboard, mouse or
floppy, the delay in printing or typing will be insignificant.
3 - I asked several platform vendors with long TCG experience, and they
said that they know of no motherboards that share the LPC bus with a TPM
plus another device.
Powered by blists - more mailing lists