Skip to content

kvm-ioctls: Make get/has/set_device_attr available on x86-64#380

Open
rbradford wants to merge 1 commit into
rust-vmm:mainfrom
rbradford:202606/device-attr-x86-64
Open

kvm-ioctls: Make get/has/set_device_attr available on x86-64#380
rbradford wants to merge 1 commit into
rust-vmm:mainfrom
rbradford:202606/device-attr-x86-64

Conversation

@rbradford

@rbradford rbradford commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Previously these were only marked as available on aarch64.

Signed-off-by: Rob Bradford rbradford@meta.com

Summary of the PR

These methods on cpu were previously only available on aarch64.

Requirements

Before submitting your PR, please make sure you addressed the following
requirements:

  • All commits in this PR have Signed-Off-By trailers (with
    git commit -s), and the commit message has max 60 characters for the
    summary and max 75 characters for each description line.
  • All added/changed functionality has a corresponding unit/integration
    test.
  • All added/changed public-facing functionality has entries in the "Upcoming
    Release" section of CHANGELOG.md (if no such section exists, please create one).
  • Any newly added unsafe code is properly documented.

Previously these were only marked as available on aarch64.

Signed-off-by: Rob Bradford <rbradford@meta.com>

@RuoqingHe RuoqingHe left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks reasonable to me, thanks @rbradford ❤️

/// let vm = kvm.create_vm().unwrap();
/// let vcpu = vm.create_vcpu(0).unwrap();
///
/// #[cfg(target_arch = "x86_64")]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we come up with a aarch64 example as well

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I agree, this would be consistent with the rest of the patch.

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.

3 participants