From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Seunghun Han <kkamagui@gmail.com>
Cc: Matthew Garrett <mjg59@google.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>,
"open list:TPM DEVICE DRIVER" <linux-integrity@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: tpm: Remove a busy bit of the NVS area for supporting AMD's fTPM
Date: Tue, 27 Aug 2019 18:11:06 +0100 [thread overview]
Message-ID: <20190827171106.owkvt6slwwg5ypyl@srcf.ucam.org> (raw)
In-Reply-To: <CAHjaAcSpU0eW5PLsEpxTkycwi+wNS67xeizb6_BMM_-qUZYAmg@mail.gmail.com>
On Wed, Aug 28, 2019 at 01:36:30AM +0900, Seunghun Han wrote:
> I got your point. Is there any problem if some regions which don't
> need to be handled in NVS area are saved and restored? If there is a
> problem, how about adding code for ignoring the regions in NVS area to
> the nvs.c file like Jarkko said? If we add the code, we can save and
> restore NVS area without driver's interaction.
The only thing that knows which regions should be skipped by the NVS
driver is the hardware specific driver, so the TPM driver needs to ask
the NVS driver to ignore that region and grant control to the TPM
driver.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2019-08-27 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 8:17 Seunghun Han
2019-08-26 17:40 ` Matthew Garrett
2019-08-27 8:23 ` Seunghun Han
2019-08-27 16:10 ` Matthew Garrett
2019-08-27 16:36 ` Seunghun Han
2019-08-27 17:11 ` Matthew Garrett [this message]
2019-08-28 9:36 ` Seunghun Han
2019-08-29 15:34 ` Jarkko Sakkinen
2019-08-29 15:39 ` Jarkko Sakkinen
2019-08-29 16:12 ` Seunghun Han
2019-08-30 10:01 ` Seunghun Han
2019-08-27 12:47 ` Jarkko Sakkinen
2019-08-27 15:49 ` 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=20190827171106.owkvt6slwwg5ypyl@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=kkamagui@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@google.com \
--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
all inboxes | Powered by JetHome®