Skip to content

Don't hardcode vCPU ID #149

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

Open
dreamliner787-9 opened this issue Mar 5, 2025 · 0 comments
Open

Don't hardcode vCPU ID #149

dreamliner787-9 opened this issue Mar 5, 2025 · 0 comments

Comments

@dreamliner787-9
Copy link
Contributor

dreamliner787-9 commented Mar 5, 2025

With the introduction of microkit_sdf_gen and support in #146, we could get rid this:

#define GUEST_VCPU_ID 0

And have the user provide the vCPU's ID as that data is provided by the tool. Because currently, if the user set the vCPU ID to anything other than zero in the metaprogram, a null cap invocation is triggered when the vCPU is resumed on VMM boot.

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

No branches or pull requests

1 participant