From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kwolf@redhat.com, Corey Bryant <coreyb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com,
jschopp@linux.vnet.ibm.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/3] TPM NVRAM persistent storage
Date: Fri, 14 Jun 2013 11:50:07 -0400 [thread overview]
Message-ID: <51BB3BAF.6020003@linux.vnet.ibm.com> (raw)
In-Reply-To: <87hah03do2.fsf@codemonkey.ws>
On 06/14/2013 11:38 AM, Anthony Liguori wrote:
> Corey Bryant <coreyb@linux.vnet.ibm.com> writes:
>
>> On 06/14/2013 10:01 AM, Anthony Liguori wrote:
>>> Corey Bryant <coreyb@linux.vnet.ibm.com> writes:
>>>
>>>> This patch series provides persistent storage support that a TPM
>>>> can use to store NVRAM data. It uses QEMU's block driver to store
>>>> data on a drive image. The libtpms TPM 1.2 backend will be the
>>>> initial user of this functionality to store data that must persist
>>>> through a reboot or migration. A sample command line may look like
>>>> this:
>>> This should be folded into the libtpms backend series.
>>>
>>> There are no users for this so this would just be untestable code in the
>>> tree subject to bitrot.
>>>
>>> Regards,
>>>
>>> Anthony Liguori
>>>
>> Fair enough. I assume you're ok with this code though?
> I don't understand why it's needed to be honest. I suspect this has to
> do with the fact that the libtpms implementation will need significant
> reworking.
libtpms does not implement a file storage layer. It neither writes data
into a FILE * nor into a QEMU BDRV. Instead it provides callbacks for
users to implement the file storage layer. Is there a problem with that?
Regards,
Stefan
>
> Regards,
>
> Anthony Liguori
>
>> --
>> Regards,
>> Corey Bryant
>>
>>>> qemu-system-x86_64 ...
>>>> -drive file=/path/to/nvram.qcow2,id=drive-nvram0-0-0
>>>> -tpmdev libtpms,id=tpm-tpm0
>>>> -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0,drive=drive-nvram0-0-0
>>>>
>>>> Thanks,
>>>> Corey
>>>>
>>>> Corey Bryant (3):
>>>> nvram: Add TPM NVRAM implementation
>>>> nvram: Add tpm-tis drive support
>>>> TPM NVRAM test
>>>>
>>>> hw/tpm/Makefile.objs | 1 +
>>>> hw/tpm/tpm_int.h | 2 +
>>>> hw/tpm/tpm_nvram.c | 324 ++++++++++++++++++++++++++++++++++++++++++++++
>>>> hw/tpm/tpm_nvram.h | 25 ++++
>>>> hw/tpm/tpm_passthrough.c | 85 ++++++++++++
>>>> hw/tpm/tpm_tis.c | 8 +
>>>> 6 files changed, 445 insertions(+), 0 deletions(-)
>>>> create mode 100644 hw/tpm/tpm_nvram.c
>>>> create mode 100644 hw/tpm/tpm_nvram.h
>>>
>>>
>>>
next prev parent reply other threads:[~2013-06-14 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 13:32 [Qemu-devel] [PATCH v3 0/3] TPM NVRAM persistent storage Corey Bryant
2013-06-06 13:32 ` [Qemu-devel] [PATCH v3 1/3] nvram: Add TPM NVRAM implementation Corey Bryant
2013-06-06 13:32 ` [Qemu-devel] [PATCH v3 2/3] nvram: Add tpm-tis drive support Corey Bryant
2013-06-07 7:41 ` [Qemu-devel] [PATCH v3 0/3] TPM NVRAM persistent storage Stefan Hajnoczi
2013-06-07 12:53 ` Corey Bryant
2013-06-14 14:01 ` Anthony Liguori
2013-06-14 15:05 ` Corey Bryant
2013-06-14 15:38 ` Anthony Liguori
2013-06-14 15:50 ` Stefan Berger [this message]
2013-06-14 15:51 ` Corey Bryant
2013-06-14 15:56 ` Anthony Liguori
2013-06-14 16:21 ` Corey Bryant
2013-06-14 18:22 ` Anthony Liguori
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=51BB3BAF.6020003@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=jschopp@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).