From: Andreas Niederl <andreas.niederl@iaik.tugraz.at>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] Add TPM 1.2 device interface
Date: Mon, 21 Feb 2011 18:03:11 +0100 [thread overview]
Message-ID: <4D629ACF.7000205@iaik.tugraz.at> (raw)
In-Reply-To: <4D5ED615.60801@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
On 02/18/2011 09:27 PM, Stefan Berger wrote:
> On 02/18/2011 12:37 PM, Andreas Niederl wrote:
[...]
>> So I'm guessing that this library is not publicly available right now?
> Not via the fedora repository at least. So yum install does not work, yet.
Is the source code available in a public version control repository?
If so, could you please provide a URI to it?
>> Is this backend meant for integration into QEMU or does it run as
>> separate process?
>>
> The backend is meant for integration in Qemu. It runs as a thread.
I see.
Has there already been an effort to integrate this with the main project?
>> How/Where could I integrate a passthrough backend like the one in this
>> patch series?
>>
> It's possible via similar mechanisms as you have, just the interface is
> bigger and main code calls into the interface at different times. I'd
> need to share the code with you.
I'd like to have a look at it.
>> The polling code isn't really necessary for the host backend, I left it
>> there just in case it would be needed by such a socket interface as is
>> used in the Xen fork.
>>
> I don't think it's necessary to have it all. In the new code, the
> frontend delivers a request to the backend and provides a callback
> function for delivering the response back once received.
Sounds good.
>>> It would certainly be desirable if your backend and mine could be
>>> accommodate.
>> Of course.
>>
> Let's see how we do this.
That would be great.
Andreas
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6163 bytes --]
next prev parent reply other threads:[~2011-02-21 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 15:33 [Qemu-devel] [PATCH 0/5] TPM device emulation Andreas Niederl
2011-02-18 15:33 ` [Qemu-devel] [PATCH 1/5] Add TPM 1.2 device interface Andreas Niederl
2011-02-18 16:37 ` Stefan Berger
2011-02-18 17:37 ` Andreas Niederl
2011-02-18 20:27 ` Stefan Berger
2011-02-21 17:03 ` Andreas Niederl [this message]
2011-02-22 16:47 ` Stefan Berger
2011-02-24 15:30 ` Andreas Niederl
2011-02-24 17:44 ` Stefan Berger
2011-02-18 21:03 ` Stefan Berger
2011-02-21 17:13 ` Andreas Niederl
2011-02-18 15:33 ` [Qemu-devel] [PATCH 2/5] Provide SSDT for enabled TPM device Andreas Niederl
2011-02-18 17:02 ` Stefan Berger
2011-02-21 16:55 ` Andreas Niederl
2011-02-18 15:33 ` [Qemu-devel] [PATCH 3/5] Add TPM host passthrough device backend Andreas Niederl
2011-02-18 15:33 ` [Qemu-devel] [PATCH 4/5] Add configure script and command line options for TPM interface Andreas Niederl
2011-02-18 15:33 ` [Qemu-devel] [PATCH 5/5] Adapt TPM host backend to use threadlets Andreas Niederl
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=4D629ACF.7000205@iaik.tugraz.at \
--to=andreas.niederl@iaik.tugraz.at \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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).