From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: flihp <flihp@twobit.us>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>, linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: add support for nonblocking operation
Date: Mon, 16 Jul 2018 20:34:11 +0300 [thread overview]
Message-ID: <20180716173411.GA5780@linux.intel.com> (raw)
In-Reply-To: <f52e541e-123e-0849-2cc7-8baf7fa39616@twobit.us>
On Thu, Jul 05, 2018 at 04:15:06PM -0700, flihp wrote:
> Thanks for reviewing the patch Jarkko. While you're doing that I took
> some time to hack up code to demonstrate the utility of supporting this
> feature. The code can be found here:
>
> https://github.com/flihp/glib-tss2-async-example
>
> In short, the example application `glib-tss2-event` uses a glib main
> event loop to create an RSA 2048 primary key in the TPM2 NULL hierarchy
> while using a glib timer event to time the operation. A GSource object
> is used to generate an event when the FD underlying the tss2 function
> call has data ready. While the application waits for an event indicating
> that the CreatePrimary operation is complete, it counts timer events
> that occur every 100ms. Once the CreatePrimary operation completes the
> number of timer events that occurred is used to make a rough calculation
> of the elapsed time. This value is then printed to the console.
>
> This takes ~300 lines of C code and requires no management or
> synchronization of threads. The glib GMainContext is "just a poll()
> loop" according to the glib documentation here:
>
> https://developer.gnome.org/programming-guidelines/stable/main-contexts.html.en
>
> and so supporting 'poll' is the easiest way to integrate with glib /
> gtk+. This is true of any other event system that relies on 'poll'
> instead of worker threads.
>
> I've tested this against the userspace resource management daemon (which
> supports 'poll') as well as the kernel interface using Tadeusz's patch
> currently under review here. If / when this gets merged feel free to add
> a "tested-by" line for myself:
> Tested-by: Philip Tricca <philip.b.tricca@intel.com>
I see the value now. I'll test this at early August when I'm back from
my leave.
Noticed now that the whole patch should be reposted because CC is missing
linux-kernel and linux-security-module (maybe with a link to your test
application in the cover letter).
/Jarkko
next prev parent reply other threads:[~2018-07-16 18:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 23:29 [PATCH] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-01 14:37 ` Jason Gunthorpe
2018-06-01 16:55 ` Tadeusz Struk
2018-06-01 17:17 ` Jason Gunthorpe
2018-06-12 0:20 ` [PATCH v2 0/2] " Tadeusz Struk
2018-06-12 0:20 ` [PATCH v2 1/2] tpm: add ptr to the tpm_space struct to file_priv Tadeusz Struk
2018-06-12 0:20 ` [PATCH v2 2/2] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-12 2:53 ` kbuild test robot
2018-06-12 4:46 ` Tadeusz Struk
2018-06-12 17:39 ` Tadeusz Struk
2018-06-04 19:55 ` [PATCH] " Jarkko Sakkinen
2018-06-04 19:56 ` Jarkko Sakkinen
2018-06-08 19:36 ` flihp
2018-06-12 0:13 ` Tadeusz Struk
2018-06-18 18:26 ` Jarkko Sakkinen
2018-06-12 1:43 ` James Bottomley
2018-06-18 18:25 ` Jarkko Sakkinen
2018-07-05 23:15 ` flihp
2018-07-16 17:34 ` Jarkko Sakkinen [this message]
2018-07-16 20:10 ` Tadeusz Struk
2018-07-23 17:38 ` Jarkko Sakkinen
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=20180716173411.GA5780@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=flihp@twobit.us \
--cc=linux-integrity@vger.kernel.org \
--cc=tadeusz.struk@intel.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