From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Seunghun Han <kkamagui@gmail.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"open list:TPM DEVICE DRIVER" <linux-integrity@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] tpm: tpm_crb: enhance command and response buffer size calculation code
Date: Tue, 10 Sep 2019 13:34:52 +0100 [thread overview]
Message-ID: <20190910123452.GC7484@linux.intel.com> (raw)
In-Reply-To: <20190909090906.28700-2-kkamagui@gmail.com>
On Mon, Sep 09, 2019 at 06:09:05PM +0900, Seunghun Han wrote:
> The purpose of crb_fixup_cmd_size() function is to work around broken
> BIOSes and get the trustable size between the ACPI region and register.
> When the TPM has a command buffer and response buffer independently,
> the crb_map_io() function calls crb_fixup_cmd_size() twice to calculate
> each buffer size. However, the current implementation of it considers
> one of two buffers.
>
> To support independent command and response buffers, I changed
> crb_check_resource() function for storing ACPI TPB regions to a list.
> I also changed crb_fixup_cmd_size() to use the list for calculating each
> buffer size.
>
> Signed-off-by: Seunghun Han <kkamagui@gmail.com>
I think as far as the tpm_crb goes I focus on getting Vanya's change
landed because it is better structured, more mature and the first
version was sent couple of weeks earlier. You are welcome to make
your remarks on that patch.
/Jarkko
next prev parent reply other threads:[~2019-09-10 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 9:09 [PATCH v2 0/2] Enhance support for the AMD's fTPM Seunghun Han
2019-09-09 9:09 ` [PATCH v2 1/2] tpm: tpm_crb: enhance command and response buffer size calculation code Seunghun Han
2019-09-10 12:34 ` Jarkko Sakkinen [this message]
2019-09-10 15:12 ` Seunghun Han
2019-09-09 9:09 ` [PATCH v2 2/2] tpm: tpm_crb: enhance resource mapping mechanism for supporting AMD's fTPM Seunghun Han
2019-09-10 14:42 ` Jarkko Sakkinen
2019-09-10 15:06 ` Jarkko Sakkinen
2019-09-10 15:28 ` Seunghun Han
2019-09-13 13:12 ` Jarkko Sakkinen
2019-09-16 8:18 ` Seunghun Han
2019-09-16 8:42 ` Seunghun Han
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=20190910123452.GC7484@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=kkamagui@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=peterhuewe@gmx.de \
/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).