Daniel Verkamp f5ee34a482 devices: virtio: initialize config MSI-X vector ... The virtio specification says that the device must have all queue and configuration change events unmapped upon reset. The queue MSI-X vector configuration was already initialized to VIRTIO_MSI_NO_VECTOR (0xffff), but the device configuration change notification vector was initialized to 0. Move the constant to the virtio module so it can be used to initialize the config vector to the correct value. BUG=chromium:854765 TEST=./build_test.py Change-Id: Ife1117e54196a898782238a2b81e69b20ac79784 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1898044 Reviewed-by: Zide Chen <zide.chen@intel.corp-partner.google.com> Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>		2019-11-06 22:20:41 +00:00
..
src	devices: virtio: initialize config MSI-X vector	2019-11-06 22:20:41 +00:00
Cargo.toml	devices: fs: Implement virtio-fs server	2019-10-27 14:26:01 +00:00