External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-07-16 14:17:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
d5f5648b37
cloud-hypervisor/vendor/registry-40351f815f426200/kvm-bindings
History
Samuel Ortiz d5f5648b37 vendor: Add vendored dependencies 
We use cargo vendor to generate a .cargo/config file and the vendor
directory. Vendoring allows us to lock our dependencies and to modify
them easily from the top level Cargo.toml.

We vendor all dependencies, including the crates.io ones, which allows
for network isolated builds.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-04 17:51:52 +02:00
..
src vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
.cargo-checksum.json vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
Cargo.toml vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
CHANGELOG.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
CONTRIBUTING.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
README.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00

README.md

Build Status Crates.io

kvm-bindings

Rust FFI bindings to KVM generated using bindgen. It currently has support for the following target architectures:

  • x86
  • x86_64
  • arm
  • arm64

Usage

First, add the following to your Cargo.toml:

kvm-bindings = "0.1"

Next, add this to your crate root:

extern crate kvm_bindings;

By default kvm-bindings will export a wrapper over the latest available kernel version (4.20), but you can select a different version by specifying it in your toml:

kvm-bindings = { version = "0.1", features = ["kvm_v4_20_0"]}

In the kvm-bindings crate each feature maps to exactly one Linux version as follows:

  • kvm_v4_14_0 contains the bindings for the Linux kernel version 4.14
  • kvm_v4_20_0 contains the bindings for the Linux kernel version 4.20