From f2acb05c33f2d4d104244b4d0b1beea1284689cc Mon Sep 17 00:00:00 2001 From: Jeongik Cha Date: Fri, 28 Jul 2023 00:16:48 +0900 Subject: [PATCH] vsock: Set BACKEND_EVENT based on NUM_QUEUES BACKEND_EVENT value depends on NUM_QUEUES, because it is the next value of NUM_QUEUES, so set it based on NUM_QUEUES Signed-off-by: Jeongik Cha --- crates/vsock/src/vhu_vsock.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/crates/vsock/src/vhu_vsock.rs b/crates/vsock/src/vhu_vsock.rs index bb59e05..eedd234 100644 --- a/crates/vsock/src/vhu_vsock.rs +++ b/crates/vsock/src/vhu_vsock.rs @@ -37,10 +37,12 @@ const TX_QUEUE_EVENT: u16 = 1; const EVT_QUEUE_EVENT: u16 = 2; /// Notification coming from the backend. -pub(crate) const BACKEND_EVENT: u16 = 3; +/// Event range [0...num_queues] is reserved for queues and exit event. +/// So NUM_QUEUES + 1 is used. +pub(crate) const BACKEND_EVENT: u16 = (NUM_QUEUES + 1) as u16; /// Notification coming from the sibling VM. -pub(crate) const SIBLING_VM_EVENT: u16 = 4; +pub(crate) const SIBLING_VM_EVENT: u16 = BACKEND_EVENT + 1; /// CID of the host pub(crate) const VSOCK_HOST_CID: u64 = 2;