arm, arm64, x86: Remove v4.14 bindings

This patch makes the bindings v4.20 the only available version for all
architectures. Because of this unique possibility, the code is
simplified, removing the specific Rust features to pick a specific
bindings version.

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>

Author: Sebastien Boeuf

.buildkite/pipeline.yml

@@ -1,11 +1,11 @@
 steps:
-  # Test release build with kernel bindings 4.14.
-  - label: "build-v4.14-x86"
+  # Test release build.
+  - label: "build-x86"
     commands:
-     - cargo build --release --features=fam-wrappers,kvm-v4_14_0
-     - cargo build --release --features=fam-wrappers,kvm-v4_14_0 --target x86_64-unknown-linux-musl
-     - cargo build --release --features=kvm-v4_14_0
-     - cargo build --release --features=kvm-v4_14_0 --target x86_64-unknown-linux-musl
+     - cargo build --release --features=fam-wrappers
+     - cargo build --release --features=fam-wrappers --target x86_64-unknown-linux-musl
+     - cargo build --release
+     - cargo build --release --target x86_64-unknown-linux-musl
     retry:
       automatic: false
     agents:
@@ -16,58 +16,10 @@ steps:
           image: "rustvmm/dev:v4"
           always-pull: true
 
-  # Test release build with kernel bindings 4.20 and fam-wrappers feature.
-  - label: "build-v4.20-x86"
+  - label: "build-arm"
     commands:
-     - cargo build --release --features=fam-wrappers,kvm-v4_20_0
-     - cargo build --release --features=fam-wrappers,kvm-v4_20_0 --target x86_64-unknown-linux-musl
-      # No need to test the kvm-v4_20_0 because that one is tested by default when no kernel bindings
-      # feature is specified.
-    retry:
-      automatic: false
-    agents:
-      platform: x86_64.metal
-      os: linux
-    plugins:
-      - docker#v3.0.1:
-          image: "rustvmm/dev:v4"
-          always-pull: true
-
-  - label: "build-v4.14-arm"
-    commands:
-      - cargo build --release --features=fam-wrappers,kvm-v4_14_0
-      - cargo build --release --features=fam-wrappers,kvm-v4_14_0 --target aarch64-unknown-linux-musl
-      - cargo build --release --features=kvm-v4_14_0
-      - cargo build --release --features=kvm-v4_14_0 --target aarch64-unknown-linux-musl
-    retry:
-      automatic: false
-    agents:
-      platform: arm.metal
-      os: linux
-    plugins:
-      - docker#v3.0.1:
-          image: "rustvmm/dev:v4"
-          always-pull: true
-
-  # Run unit tests for 4.14 bindings. These are the only ones that are not run by the rust-vmm-ci.
-  - label: "unittests-v4.14-x86"
-    command:
-      - cargo test --features=kvm-v4_14_0
-      - cargo test --features=kvm-v4_14_0 --target x86_64-unknown-linux-musl
-    retry:
-      automatic: false
-    agents:
-      platform: x86_64.metal
-      os: linux
-    plugins:
-      - docker#v3.0.1:
-          image: "rustvmm/dev:v4"
-          always-pull: true
-
-  - label: "unittests-v4.14-arm"
-    command:
-      - cargo test --features=kvm-v4_14_0
-      - cargo test --features=kvm-v4_14_0 --target aarch64-unknown-linux-musl
+      - cargo build --release --features=fam-wrappers
+      - cargo build --release --features=fam-wrappers --target aarch64-unknown-linux-musl
     retry:
       automatic: false
     agents:
@@ -80,9 +32,7 @@ steps:
 
   - label: "check-warnings-x86"
     commands:
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_14_0,fam-wrappers
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_20_0,fam-wrappers
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_14_0
+      - RUSTFLAGS="-D warnings" cargo check --features=fam-wrappers
     retry:
       automatic: false
     agents:
@@ -96,9 +46,7 @@ steps:
 
   - label: "check-warnings-arm"
     commands:
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_14_0,fam-wrappers
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_20_0,fam-wrappers
-      - RUSTFLAGS="-D warnings" cargo check --features=kvm-v4_14_0
+      - RUSTFLAGS="-D warnings" cargo check --features=fam-wrappers
     retry:
       automatic: false
     agents:

CONTRIBUTING.md

@@ -21,7 +21,7 @@ git clone https://github.com/torvalds/linux.git
 When adding a new architecture, the bindings must be generated for all existing
 versions for consistency reasons.
 
-### Example for arm64 and version 4.14 and 4.20
+### Example for arm64 and version 4.20
 
 For this example we assume that you have both linux and kvm-bindings
 repositories in your root.

Cargo.toml

@@ -9,8 +9,6 @@ keywords = ["kvm"]
 license = "Apache-2.0"
 
 [features]
-kvm-v4_14_0 = []
-kvm-v4_20_0 = []
 fam-wrappers = ["vmm-sys-util"]
 
 [dependencies]

README.md

@@ -28,23 +28,13 @@ Next, add this to your crate root:
 ```rust
 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:
-```toml
-kvm-bindings = { version = "0.3", features = ["kvm_v4_20_0"]}
-```
-Bindings are generated for each specific Linux kernel version based on the enabled
-crate features 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
 
 This crate also offers safe wrappers over FAM structs - FFI structs that have
 a Flexible Array Member in their definition.
 These safe wrappers can be used if the `fam-wrappers` feature is enabled for
 this crate. Example:
 ```toml
-kvm-bindings = { version = "0.3", features = ["kvm_v4_20_0", "fam-wrappers"]}
+kvm-bindings = { version = "0.3", features = ["fam-wrappers"]}
 ```
 
 # Dependencies