crosvm/vfio_sys/Cargo.toml

[package]
name = "vfio_sys"
version = "0.1.0"
authors = ["The Chromium OS Authors"]
edition = "2018"

[dependencies]
base = { path = "../base" }
vfio_sys: Add vfio.h to vfio_sys Import kernel include/uapi/linux/vfio.h, it define ioctl interface. BUG=none TEST=none Change-Id: If8e0dae22cb566ae32dfd61d6f2b147f56727611 Signed-off-by: Xiong Zhang <xiong.y.zhang@intel.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1580456 Tested-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 2019-04-23 09:08:18 +00:00			`[package]`
			`name = "vfio_sys"`
			`version = "0.1.0"`
			`authors = ["The Chromium OS Authors"]`
			`edition = "2018"`

			`[dependencies]`
Add "base" crate and transition crosvm usages to it from sys_util For now, this crate simply re-exports all of sys_util, but it will be updated to provide new interfaces when needed. This is the first step to making crosvm not directly depend on sys_util, so that we can make the interface changes we need without fear of negatively affecting (i.e. completely breaking) other usages within chromeos. BUG=b:162363783 TEST=./build_test Change-Id: I7d0aa3d8a1f66af1c7fee8fd649723ef17027150 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2325168 Tested-by: Michael Hoyle <mikehoyle@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Michael Hoyle <mikehoyle@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> 2020-08-03 03:09:41 +00:00			`base = { path = "../base" }`