-
Notifications
You must be signed in to change notification settings - Fork 109
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
ARM Support #8
Comments
I'll take a look at these missing bullets in the reverse order they're listed, i.e. starting with the run_code example. |
|
@michael2012z we currently use the v4.20 bindings. So probably we want to have the ioctls that are available in 4.20. We didn't discuss about adding bindings to newer kernel versions. I think we can send an email to rust-vmm to see what other people think about this. I don't really have strong preferences here. If the ioctls available in newer versions have associated caps that we can check before calling them, it should be okay to add them directly. Otherwise we might want to use rust features to disable them by default. |
Typically caps are also added or enabled with new API. When KVM_GET_VCPU_EVENTS and KVM_SET_VCPU_EVENTS were introduced to arm KVM_CAP_VCPU_EVENTS was enabled. As Andreea says, rust-vmm should check caps whenever possible before using their associated features. |
@andreeaflorescu @rhdrjones Thanks. |
Arm support is already added to kvm-ioctls. There are a still improvements needed (such as on the documentation), but these are tracked in separate issues. |
Currently kvm-ioctls only has support for x86_64.
run_code
example with ARMThe text was updated successfully, but these errors were encountered: