vmm_vhost: renumber SHARED_MEMORY_REGIONS

0x0002_0000 is now standardized as VHOST_USER_PROTOCOL_F_XEN_MMAP[1].
Renumber SHARED_MEMORY_REGIONS to an available value to avoid
interoperability problems with other vhost-user implementations.

(It would be nice if VHOST_USER_PROTOCOL_F_SHARED_MEMORY was
standardised, to avoid this problem in future!)

[1]: f21e95ee97

TEST=run crosvm vhost-user-gpu device with cross domain

Change-Id: I56c36e5ef75b68fd4244dee1206a2cd1bee7c452
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4727935
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
This commit is contained in:
Alyssa Ross 2023-07-29 12:03:18 +00:00 committed by crosvm LUCI
parent 708fb72f3b
commit 6795b3edf3

View file

@ -443,8 +443,10 @@ bitflags! {
const CONFIGURE_MEM_SLOTS = 0x0000_8000;
/// Support reporting status.
const STATUS = 0x0001_0000;
/// Support shared memory regions.
const SHARED_MEMORY_REGIONS = 0x0002_0000;
/// Support Xen mmap.
const XEN_MMAP = 0x0002_0000;
/// Support shared memory regions. (Non-standard.)
const SHARED_MEMORY_REGIONS = 0x8000_0000;
}
}