Adds crypto algorithm performance testing harness #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds a GitHub Action-based test harness, which builds the Linux Kernel as a User-mode Linux binary, and runs the test script placed on the zeta/test-artifacts/test-script.sh file.
ignatk
reviewed
Oct 9, 2023
zeta/test-artifacts/init
Outdated
|
|
||
| ./test-script.sh | ||
|
|
||
| mkdir /proc |
There was a problem hiding this comment.
how can we use mkdir directly, but not mount?
nit: you can probably avoid this by just creating /proc in initrd directory during build time
There was a problem hiding this comment.
It's a good question, can't tell for sure. It seems the busybox shell links some utilities out-of-the-box, but not others, but can't find exactly where that's happening.
Removed the /proc directory creation on the latest version, and we're now calling the busybox install command before invoking anything else so that we have all symlinks created.
Add /proc directory to the initramfs structure, rather than creating it as part of the init script. Make busybox install the links to the builtin utilities as part of the init script, so that commands don't have to be prepended with busybox (which seemed to only be required in some cases). Modify the kernel make directive to use the number of processor cores available to the Github runner to speed up the build process.
ignatk
approved these changes
Oct 11, 2023
armfazh
force-pushed
the
jlima/crypto-test-harness
branch
2 times, most recently
from
19d48df to
47e118f
Compare
armfazh
force-pushed
the
jlima/crypto-test-harness
branch
from
47e118f to
d9df7e5
Compare
armfazh
approved these changes
Oct 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds crypto algorithm performance testing pipeline, built as a GitHub Action-based test harness.
The testing pipeline runs the Linux Kernel as a User-mode Linux binary.
The Linux Kernel test binary is built from the configuration specified in
zeta/test-artifacts/config-um, and a simple initramfs archive is created, including the busybox binary, the init and test scripts (/zeta/test-artifacts/init and /zeta/test-artifacts/test-script.sh), and any kernel modules resulting from the kernel build.The crypto algorithm performance test consists in running the tcrypt kernel testing utility against each of the algorithms being tested - since the user-mode linux binary kernel doesn't have access to a high-resolution timer, the test relies on execution time to compare the different algorithm implementations.