From: <Alexander.Steffen@infineon.com>
To: <jarkko.sakkinen@linux.intel.com>
Cc: <shuahkh@osg.samsung.com>, <linux-integrity@vger.kernel.org>
Subject: TPM tests within kselftest?
Date: Thu, 14 Dec 2017 16:23:29 +0000 [thread overview]
Message-ID: <0d71b9ee00a14b689896cac1dcbb6a12@infineon.com> (raw)
Hi Jarkko,
during the Kernel Summit in Prague I talked with Shuah Khan about kselftest and the possibility to integrate TPM tests into that framework. What would you think about your tests (https://github.com/jsakkine-intel/tpm2-scripts) living there?
This way, those tests would get more visibility/popularity with other developers, and thus hopefully more contributors that can use that framework as a starting point. It also allows us to have a common test set, that all TPM developers can easily use for their work. And the tests being integrated into the kernel repository would avoid issues like I had just now, where your new test for invalid command codes failed when I tried to run it on an older kernel that did not have that functionality implemented.
Currently, most tests within kselftest are not implemented in Python, but Shuah did not sound strictly opposed to that idea. In fact, some Python-based tests already have made it into the tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/tc-testing), though they do not seem to be called by kselftest by default.
Alexander
next reply other threads:[~2017-12-14 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 16:23 Alexander.Steffen [this message]
2017-12-15 14:46 ` TPM tests within kselftest? 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=0d71b9ee00a14b689896cac1dcbb6a12@infineon.com \
--to=alexander.steffen@infineon.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=shuahkh@osg.samsung.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