-
Notifications
You must be signed in to change notification settings - Fork 98
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
Configure NVMe keep-alive ability from host #487
base: main
Are you sure you want to change the base?
Conversation
@@ -225,6 +225,11 @@ fn build_kernel_command_line( | |||
)?; | |||
} | |||
|
|||
// Only when explicitly supported by Host. | |||
if partition_info.nvme_keepalive && !partition_info.vtl2_pool_memory.is_empty() { |
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.
We should pass this via DT to usermode, the env args are for test/unstable features.
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.
Although if we want to keep it as unstable (env arg only), lets file a cleanup issue to track cleaning this up.
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.
okay, after your change I thought you wanted to keep it as command-line
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.
After further thinking I suggest to keep it as an env var for now and clanup later.
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.
Inform OpenHCL that Host is compatible with NVMe keep-alive feature by adding a new device tree entry
/openhcl/vf-keepalive=nvme
where vf-keepalive is a list of strings which may be expanded in future to include other device types such as
vf-keepalive=nvme,mana
During servicing operation the host must now explicitly indicate that NVMe data should be saved (if VM supports it), this change flips the definition of keepalive bit in capabilities_flags bitmask (it used to be an emergency shut-off, not it is an "allow" indication). This flipping resolves compatibility issues with older host OSes after Live Migration.