uhyve 0.8.0

A specialized hypervisor for Hermit
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84

//! Virtio Datastructures and constants.

pub(crate) mod capabilities;
pub(crate) mod net;
pub(crate) mod pci;

pub mod features {
	use virtio_bindings::{
		bindings::virtio_net::{VIRTIO_NET_F_MAC, VIRTIO_NET_F_MTU, VIRTIO_NET_F_STATUS},
		virtio_config::VIRTIO_F_VERSION_1,
	};

	pub const UHYVE_NET_FEATURES_LOW: u32 =
		1 << VIRTIO_NET_F_MAC | 1 << VIRTIO_NET_F_STATUS | 1 << VIRTIO_NET_F_MTU;
	pub const UHYVE_NET_FEATURES_HIGH: u32 = ((1_usize << VIRTIO_F_VERSION_1) >> 32) as u32;
}

use bitflags::bitflags;
use zerocopy::{Immutable, IntoBytes};

pub(crate) const QUEUE_LIMIT: usize = 256;

// A virtqueue notification as described in the Virtio standard v1.2 Sec. 2.9 & 4.1.5.2.
#[repr(C)]
#[derive(IntoBytes, Debug, Default, Immutable)]
pub struct VirtqueueNotification {
	/// VQ number to be notified
	pub vqn: u16,
	/// next_off: Offset within the ring to the next available ring entry (lower 15 bytes)
	/// wrap: wrap counter (msb)
	pub next_off_wrap: u16,
}

/// Virtio device status field. See section 2.1 virtio v1.2
#[derive(Copy, Clone, Debug, IntoBytes, PartialEq, Eq, Immutable)]
#[repr(C)]
pub struct DeviceStatus(u16);
bitflags! {
	impl DeviceStatus : u16 {
		/// Despite not being a valid virtio Flag, 0 represents an uninitialized or reset device.
		const UNINITIALIZED = 0;
		/// Indicates the guest has found the device and recognises it as valid.
		const ACKNOWLEDGE = 1;

		/// Indicates the guest knows how to drive the device.
		const DRIVER = 2;

		/// Indicates the driver is set up and ready to drive the device.
		const DRIVER_OK = 4;

		/// indicates the driver has acknowledged the features it understands and negotiation is
		/// complete.
		const FEATURES_OK = 8;

		/// Indicates that the device has experienced an error from which it can’t recover.
		const DEVICE_NEEDS_RESET = 64;

		/// Indicates that the PCI capabilities pointer points to a linked list at register address
		/// 0x34.
		///
		/// See: PCI-to-PCI bridge architechture, section 3.2.4.4
		const PCI_CAPABILITIES_LIST_ENABLE = 16;

		/// Failed to initialize.
		const FAILED = 128;
	}
}

// Virtio Device IDs.
//
// The device is calculated by adding 0x1040 to the virtio device ID as in section 5, or have a
// transitional device ID.
//
// See sections 4.1.2.1 and 5 virtio v1.2
const ROOT_DEVICE_ID: u16 = 0x1040;
pub const NET_DEVICE_ID: u16 = ROOT_DEVICE_ID + 1;
const _BLOCK_DEVICE_ID: u16 = ROOT_DEVICE_ID + 2;
const _CONSOLE_DEVICE_ID: u16 = ROOT_DEVICE_ID + 3;
const _SOCKET_DEVICE_ID: u16 = ROOT_DEVICE_ID + 19;

/// Virtio PCI vendor ID, section 4.1.2 v1.2
pub const VIRTIO_VENDOR_ID: u16 = 0x1AF4;

const VIRTIO_MSI_NO_VECTOR: u16 = 0xffff;