Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

yupavlen-ms
Copy link
Contributor

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.

@yupavlen-ms yupavlen-ms requested a review from a team as a code owner December 16, 2024 17:14
@@ -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() {
Copy link
Member

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.

Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Contributor Author

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants