linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kgold@linux.vnet.ibm.com (Ken Goldman)
To: linux-security-module@vger.kernel.org
Subject: [Linux-ima-devel] [tpmdd-devel] [PATCH] tpm: improve tpm_tis send() performance by ignoring burstcount
Date: Fri, 11 Aug 2017 17:42:43 -0400	[thread overview]
Message-ID: <7ec8265f-265d-641a-6da3-d931f8df4819@linux.vnet.ibm.com> (raw)
In-Reply-To: <db0359cc-5e6b-2055-734a-bd9104e4a99f@linux.vnet.ibm.com>

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-11 21:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 11:46 [PATCH] tpm: improve tpm_tis send() performance by ignoring burstcount Nayna Jain
2017-08-07 11:52 ` Peter Huewe
2017-08-07 14:25   ` Nayna
2017-08-08 21:50     ` Jarkko Sakkinen
2017-08-08 19:11   ` Jarkko Sakkinen
2017-08-09 20:23     ` [tpmdd-devel] " Ken Goldman
2017-08-09 20:43       ` Aw: " Peter Huewe
2017-08-11 21:54         ` Ken Goldman
     [not found]           ` <20170814101046.5hqrkaqmfvl7ugwj@linux.intel.com>
2017-08-16 19:51             ` Ken Goldman
2017-08-09 20:25     ` Ken Goldman
2017-08-09 21:00       ` Aw: " Peter Huewe
2017-08-11 11:14         ` Jarkko Sakkinen
2017-08-11 15:30           ` Mimi Zohar
2017-08-14 10:51             ` Jarkko Sakkinen
2017-08-14 10:56               ` Jarkko Sakkinen
2017-08-14 12:03                 ` Mimi Zohar
2017-08-15  6:08                   ` Jarkko Sakkinen
2017-08-14 12:12                 ` Mimi Zohar
2017-08-15  6:09                   ` Jarkko Sakkinen
2017-08-11 21:32         ` Aw: " Ken Goldman
2017-08-13 23:53           ` msuchanek
2017-08-15 22:02             ` Ken Goldman
2017-08-16 10:24               ` Michal Suchánek
2017-08-11 21:42       ` Ken Goldman [this message]
2017-08-08 19:07 ` Jarkko Sakkinen

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=7ec8265f-265d-641a-6da3-d931f8df4819@linux.vnet.ibm.com \
    --to=kgold@linux.vnet.ibm.com \
    --cc=linux-security-module@vger.kernel.org \
    /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).