arm64, x86: Update bindings to v5.13

Replace the v4.20 bindings with the up to date v5.13 ones. The `arm`
architecture is now covered with the `arm64` bindings the same way both
`x86` and `x86_64` are covered by the bindings from `x86_64`.

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

Author: Sebastien Boeuf

.buildkite/pipeline.yml

@@ -13,7 +13,7 @@ steps:
       os: linux
     plugins:
       - docker#v3.0.1:
-          image: "rustvmm/dev:v4"
+          image: "rustvmm/dev:v12"
           always-pull: true
 
   - label: "build-arm"
@@ -27,7 +27,7 @@ steps:
       os: linux
     plugins:
       - docker#v3.0.1:
-          image: "rustvmm/dev:v4"
+          image: "rustvmm/dev:v12"
           always-pull: true
 
   - label: "check-warnings-x86"
@@ -41,7 +41,7 @@ steps:
     plugins:
       - docker#v3.0.1:
           privileged: true
-          image: "rustvmm/dev:v4"
+          image: "rustvmm/dev:v12"
           always-pull: true
 
   - label: "check-warnings-arm"
@@ -55,5 +55,5 @@ steps:
     plugins:
       - docker#v3.0.1:
           privileged: true
-          image: "rustvmm/dev:v4"
-          always-pull: true
+          image: "rustvmm/dev:v12"
+          always-pull: true

CONTRIBUTING.md

@@ -4,9 +4,9 @@
 
 ### Bindgen
 The bindings are currently generated using
-[bindgen](https://crates.io/crates/bindgen) version 0.46.0:
+[bindgen](https://crates.io/crates/bindgen) version 0.59.1:
 ```bash
-cargo install bindgen --vers 0.46.0
+cargo install bindgen --vers 0.59.1
 ```
 
 ### Linux Kernel
@@ -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.20
+### Example for arm64 and version 5.13
 
 For this example we assume that you have both linux and kvm-bindings
 repositories in your root.
@@ -35,22 +35,22 @@ cd ~
 # linux is the repository that you cloned at the previous step.
 cd linux
 # Step 2: Checkout the version you want to generate the bindings for.
-git checkout v4.20
+git checkout v5.13
 
 # Step 3: Generate the bindings.
 # This will generate the headers for the targeted architecture and place them
 # in the user specified directory. In this case, we generate them in the
-# arm64_v4_20_headers directory.
-make headers_install ARCH=arm64 INSTALL_HDR_PATH=arm64_v4_20_headers
-cd arm64_v4_20_headers
-bindgen include/linux/kvm.h -o bindings_v4_20_0.rs \
-  --with-derive-default
-  --with-derive-partialeq
+# arm64_v5_13_headers directory.
+make headers_install ARCH=arm64 INSTALL_HDR_PATH=arm64_v5_13_headers
+cd arm64_v5_13_headers
+bindgen include/linux/kvm.h -o bindings_v5_13_0.rs \
+  --with-derive-default \
+  --with-derive-partialeq \
   -- -Iinclude
 cd ~
 
 # Step 4: Copy the generated file to the arm64 module.
-cp linux/arm64_v4_20_headers/bindings_v4_20_0.rs
+cp linux/arm64_v5_13_headers/bindings_v5_13_0.rs
 ```
 
 Steps 2, 3 and 4 must be repeated for each of the existing KVM versions. Don't

coverage_config_x86_64.json

@@ -1,5 +1,5 @@
 {
-  "coverage_score": 68.3,
+  "coverage_score": 66.3,
   "exclude_path": "",
   "crate_features": "fam-wrappers"
 }