From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2 4/9] Add tpm_tis driver to build process
Date: Mon, 04 Apr 2011 22:08:50 -0400 [thread overview]
Message-ID: <4D9A79B2.2010502@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTinmGwEfG25_VhNvr6QBXwQ7qu=mtA@mail.gmail.com>
On 04/03/2011 05:20 AM, Blue Swirl wrote:
> On Fri, Apr 1, 2011 at 10:57 PM, Stefan Berger
> <stefanb@linux.vnet.ibm.com> wrote:
>> On 04/01/2011 02:14 PM, Blue Swirl wrote:
>>
>> At this point there is no compile test needed since all code is 'there'.
>> It's merely adding the front-end,i.e., the TPM TIS emulation to be compiled.
> If the basic device (without the tpms-devel library) can be built on
> any OS, the flag should go to default-configs/*86*-softmmu.mak.
>
It can be built on any OS, but it is of no use since the backend
(libtpms) is only available on Linux and we don't support it on another
OS. Unless someone else wants to port it to other OSes, I'd say that the
test for Linux is useful.
I'd actually also only compile the TIS if libtpms could be found, and
terminate with an error message otherwise. I would add this restriction
only in the last patch, so that in patch 4 at least for now the TIS can
be built. Does that sound reasonable?
>> The (libtpms-based) backend is then added later in patch [9/9]. There you
>> then find this here:
>>
>> if test "$has_tpm" = "1"; then
>> + if test -r /usr/include/libtpms/tpm_library.h ; then
> Here you make assumptions on the header file location, but it could be
> in /usr/local, /opt or somewhere where the cross compiler happens to
> find it. Please just do the compile test.
>
Fixed that.
Stefan
next prev parent reply other threads:[~2011-04-05 2:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 19:42 [Qemu-devel] [PATCH V2 0/9] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 1/9] Support for TPM command line options Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 2/9] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 3/9] Add persistent state handling to TPM TIS frontend driver Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 4/9] Add tpm_tis driver to build process Stefan Berger
2011-04-01 18:14 ` Blue Swirl
2011-04-01 19:57 ` Stefan Berger
2011-04-03 9:20 ` Blue Swirl
2011-04-05 2:08 ` Stefan Berger [this message]
2011-04-05 17:45 ` Blue Swirl
2011-04-05 18:33 ` Stefan Berger
2011-04-05 18:55 ` Blue Swirl
2011-04-06 0:12 ` Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 5/9] Add a debug register Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 6/9] Implement qemu_thread_join function Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 7/9] Add a TPM backend skeleton implementation Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 8/9] Implementation of the libtpms-based backend Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 9/9] Add block storage support for libtpms based TPM backend Stefan Berger
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=4D9A79B2.2010502@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).