rust-kernel
Rustbelt: a hobby x86_64 kernel written in Rust
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 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 | //! Driver for virtio-blk: the paravirtual disk QEMU/KVM offer
//! (`-drive file=disk.img,if=virtio`).
//!
//! Why virtio and not ATA PIO? ATA PIO is simpler (copy 256 words through an
//! I/O port per sector) but it's a 1980s interface that real machines barely
//! have any more. virtio is what VMs actually use, and it teaches the core
//! idea of every modern device: *shared memory queues + DMA*. We use the
//! **legacy** (virtio 0.9.5) interface, which QEMU's "transitional" virtio
//! devices still offer: its registers are a handful of I/O ports (BAR0), and
//! setting it up is ~40 lines. The modern (1.0) interface uses PCI
//! capabilities + MMIO; the queue format is the same.
//!
//! The virtqueue: three arrays in physical memory that driver and device share.
//! * descriptor table: {physical addr, length, flags, next} -- buffers
//! * available ring: driver writes "descriptor chain N is ready"
//! * used ring: device writes "I finished chain N"
//! A block request is a chain of 3 descriptors:
//! header {type: read/write, sector} -> data (512*n bytes) -> status byte
//! We put the chain in the available ring, write the queue number to the
//! "notify" port, and wait until the used ring's index moves.
//!
//! Simplifications: one request at a time; we *poll* the used ring instead of
//! using the interrupt (we even ask the device not to interrupt us), and we
//! copy data through one page-sized "bounce buffer", so a request moves at
//! most 8 sectors. Reference: virtio spec 1.2 sections 2.7 (split virtqueues),
//! 4.1.4.8 (legacy PCI interface), 5.2 (block device); wiki.osdev.org/Virtio
use ;
use crateErrno;
use cratememory;
use cratePciDevice;
use ;
use ;
use Mutex;
use PhysAddr;
use Port;
// Legacy virtio PCI registers (offsets into the I/O BAR).
const REG_DEVICE_FEATURES: u16 = 0x00;
const REG_GUEST_FEATURES: u16 = 0x04;
const REG_QUEUE_ADDRESS: u16 = 0x08; // physical page number of the queue
const REG_QUEUE_SIZE: u16 = 0x0c;
const REG_QUEUE_SELECT: u16 = 0x0e;
const REG_QUEUE_NOTIFY: u16 = 0x10;
const REG_DEVICE_STATUS: u16 = 0x12;
const REG_ISR_STATUS: u16 = 0x13;
const REG_CAPACITY: u16 = 0x14; // device config: disk size in sectors (u64)
// Device status bits (we tell the device how far initialization got).
const STATUS_ACKNOWLEDGE: u8 = 1; // "I see you"
const STATUS_DRIVER: u8 = 2; // "I know how to drive you"
const STATUS_DRIVER_OK: u8 = 4; // "ready to go"
// Descriptor flags.
const DESC_NEXT: u16 = 1; // chain continues at `next`
const DESC_WRITE: u16 = 2; // device writes into this buffer (vs. reads it)
const AVAIL_NO_INTERRUPT: u16 = 1; // "don't interrupt me, I'm polling"
const REQ_READ: u32 = 0; // VIRTIO_BLK_T_IN
const REQ_WRITE: u32 = 1; // VIRTIO_BLK_T_OUT
/// Max sectors per request = what fits in our one-page bounce buffer.
const MAX_SECTORS: usize = 4096 / SECTOR_SIZE;
/// PCI vendor 0x1af4 (Red Hat/virtio), device 0x1001 = transitional block device.
|