From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: tpmdd-devel@lists.sourceforge.net
Cc: linux-security-module@vger.kernel.org,
Jerry Snitselaar <jsnitsel@redhat.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v3 0/3] Locality support for tpm_crb
Date: Wed, 8 Feb 2017 13:11:34 +0200 [thread overview]
Message-ID: <20170208111137.15153-1-jarkko.sakkinen@linux.intel.com> (raw)
The tpm_crb driver should follow the policy of reserving and
relinquishing the locality it uses when multiple localities are used,
like when TXT is another locality.
[This is a resend of v3 as this has been asked from me for a few times
now and there wasn't anything obvious to fix.]
Jarkko Sakkinen (3):
tpm_crb: map locality registers
tpm_crb: encapsulate crb_wait_for_reg_32
tpm_crb: request and relinquish locality 0
drivers/char/tpm/tpm_crb.c | 185 +++++++++++++++++++++++++++++++++------------
1 file changed, 137 insertions(+), 48 deletions(-)
--
v2:
added sanity check for start address of the control area
v3:
do locality request/relinquish as part of send/recv
check priv->regs_h before using it
just assing the base address to regs_h instead of using crb_map_res
2.9.3
next reply other threads:[~2017-02-08 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 11:11 Jarkko Sakkinen [this message]
2017-02-08 11:11 ` [PATCH v3 1/3] tpm_crb: map locality registers Jarkko Sakkinen
2017-02-08 11:11 ` [PATCH v3 2/3] tpm_crb: encapsulate crb_wait_for_reg_32 Jarkko Sakkinen
2017-02-08 11:11 ` [PATCH v3 3/3] tpm_crb: request and relinquish locality 0 Jarkko Sakkinen
2017-03-04 1:27 ` [PATCH v3 0/3] Locality support for tpm_crb Jerry Snitselaar
2017-03-06 15:35 ` Jarkko Sakkinen
2017-03-07 16:41 ` Wei, Gang
2017-03-07 18:31 ` Jarkko Sakkinen
2017-03-07 10:41 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2016-12-07 11:49 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=20170208111137.15153-1-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jsnitsel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®