-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new version of the restricted kernel simple_io and initrd #4906
Add new version of the restricted kernel simple_io and initrd #4906
Conversation
the new oak_restricted_kernel_simple_io_init_rd_wrapper will exist alongside oak_restricted_kernel_simple_io_wrapper for a while. then internal dependencies will be updated, and the the former will be removed. this approach is significatnly simpler than #. For project-oak#4828 we would need to attempt to synchronize its merging with the updates to the internal launcher and the transparent release imports of the binary. It'd be too flaky.
@@ -42,6 +43,7 @@ readonly generated_binaries=( | |||
) | |||
readonly binary_names=( | |||
oak_restricted_kernel_simple_io_wrapper_bin | |||
oak_restricted_kernel_simple_io_init_rd_wrapper_bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume the new one would also behave like a bzImage (i.e. a kernel-type endorsement) since it is named "wrapper".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
@@ -42,6 +43,7 @@ readonly generated_binaries=( | |||
) | |||
readonly binary_names=( | |||
oak_restricted_kernel_simple_io_wrapper_bin | |||
oak_restricted_kernel_simple_io_init_rd_wrapper_bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
the new oak_restricted_kernel_simple_io_init_rd_wrapper will exist alongside oak_restricted_kernel_simple_io_wrapper for a while. then internal dependencies will be updated, and the the former will be removed.
this approach is significantly simpler than #4828. For #4828 we would need to attempt to synchronize its merging with the updates to the internal launcher and the transparent release imports of the binary. It'd be too flaky.