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 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 | //! Build script, two jobs:
//!
//! 0. Compile the vDSO (vdso/, stage 19) into OUT_DIR/vdso.so.
//!
//! 1. Compile the user programs in user/ into ELF executables in OUT_DIR
//! (stage 19: also C programs against musl, see `MUSL_PROGRAMS`).
//! They're compiled with plain `rustc` for the built-in
//! `x86_64-unknown-none` target (prebuilt `core`, so no build-std
//! needed), as static executables (`relocation-model=static`) linked at a
//! high user address -- which needs the `large` code model (the default
//! ones assume code in the low/high 2 GiB).
//!
//! 2. Build the second QEMU disk, `target/disk.img` (64 MiB):
//! * a GPT partition table (made with `sfdisk`) with one partition
//! starting at sector 2048 (1 MiB, the usual alignment),
//! * in it a FAT32 file system (`mkfs.vfat`), filled with `mtools`
//! (`mmd`/`mcopy` write into an image file directly -- no root, no
//! loop-mounting needed): everything in disk/ plus the user programs
//! in /bin.
//! The kernel finds the disk on the PCI bus, reads the GPT, mounts the
//! FAT32 partition at /mnt/disk0 and loads programs from /mnt/disk0/bin.
//! QEMU opens it with `snapshot=on`, so the kernel's writes never change
//! this file (every boot and every test starts from the same disk).
//!
//! 3. Build the third QEMU disk, `target/ext2.img` (32 MiB): a whole-disk
//! ext2 file system (no partition table) made by `mke2fs -d`, which
//! copies a directory tree into the new file system. The tree is disk2/
//! plus generated files: big.txt (big enough for double-indirect blocks),
//! sparse.bin (66 MiB of mostly holes, reaching the triple-indirect
//! blocks), and two symlinks (one short = "fast", one long = "slow").
//! Mounted at /mnt/disk1 (drive C: in the shell).
//! Two more small images are for `cargo test` only (see Cargo.toml
//! test-args): ext2-4k.img (4 KiB blocks) and ext2-rev0.img (the original
//! 1993 revision 0 format: fixed 128-byte inodes, no file types in
//! directory entries).
//!
//! 4. Build the fourth QEMU disk, `target/exfat.img` (32 MiB): a whole-disk
//! exFAT file system. `mkfs.exfat` formats it, but no tool can copy files
//! into an exFAT image without mounting it (root or a loop device), so
//! build/exfat_populate.rs does that itself: a small exFAT writer of its
//! own, separate from the kernel's driver. The tree is disk3/ (long
//! names with spaces, mixed case, non-ASCII) plus numbers.txt (340 KB,
//! contiguous) and frag-chain.txt (fragmented, linked through the FAT).
//! Mounted at /mnt/disk2 (drive D:). exfat-512.img (512-byte clusters,
//! so everything spans many clusters) is for `cargo test` only.
//!
//! 5. Build the fifth QEMU disk, `target/btrfs.img` (128 MiB): a btrfs file
//! system made by `mkfs.btrfs --rootdir`, which (like `mke2fs -d`) copies
//! a directory tree in. The tree is disk4/ plus generated files: big.txt
//! (2 MiB of text: many compressed extents), random.bin (incompressible,
//! so stored uncompressed), zeros.bin, empty.txt and symlinks.
//! `--compress zlib` compresses it; `-u projects -u ro:archive` turns
//! those two directories into subvolumes. Mounted at /mnt/disk3 (E:).
//! For `cargo test` only: the same tree with lzo and 4 KiB B-tree nodes
//! (deeper trees), with zstd and 64 KiB nodes, a btrfs made by
//! `btrfs-convert` from an ext2 image (the only way to get real holes
//! and extents shared by several files without mounting anything), and
//! one with sha256 checksums, which the driver must refuse.
//! It also writes manifests (target/btrfs-*.manifest): every path with
//! its size and CRC-32, which tests/btrfs.rs and scripts/btrfs-check.sh
//! compare with what Rustbelt reads.
//!
//! Needs dosfstools (mkfs.vfat), mtools (mmd, mcopy), fdisk (sfdisk),
//! e2fsprogs (mke2fs), exfatprogs (mkfs.exfat) and btrfs-progs
//! (mkfs.btrfs, btrfs-convert):
//! sudo apt install dosfstools mtools fdisk e2fsprogs exfatprogs btrfs-progs
use ;
/// Everything in /bin on the disk: the shell, its tools, and the test and
/// demo programs of the earlier stages.
const PROGRAMS: & = &;
/// C programs in /bin, built with the host's C compiler and no libc at all:
/// plain Linux binaries that check Rustbelt speaks the Linux ABI.
const C_PROGRAMS: & = &; // stage 15.1
/// Stage 19: C programs built against a real C library, musl, with the
/// `musl-gcc` wrapper (Debian/Ubuntu: `sudo apt install musl-tools`).
const MUSL_PROGRAMS: & = &;
const DISK_SECTORS: u64 = 64 * 1024 * 1024 / 512;
const PART_START: u64 = 2048;
/// Leave 1 MiB at the end too (the backup GPT lives in the last 33 sectors).
const PART_SECTORS: u64 = DISK_SECTORS - 2 * PART_START;
/// A freestanding C program: no libc, no startup files, just raw syscalls.
/// -fpie makes the code RIP-relative so it can live at Rustbelt's user base
/// (0x80_0000_0000, above 4 GiB); -no-pie still makes an ordinary static
/// ET_EXEC file, which also runs as-is on a real x86_64 Linux machine.
/// The vDSO (stage 19, see vdso/vdso.c): a tiny shared library the kernel
/// maps into every process; src/vdso.rs embeds the result with
/// `include_bytes!`. -fPIC and no libc: it has to work at any address and
/// without anything else loaded. The linker script vdso/vdso.lds lays it
/// out as one page (ELF header first) and names the version LINUX_2.6;
/// --hash-style=both writes the old SysV hash table too, which musl needs.
/// A C program linked with musl (stage 19).
///
/// StaticExec: the ELF type the stock recipe makes (ET_EXEC), but moved to
/// Rustbelt's user base (0x80_0000_0000; the kernel owns the low addresses)
/// with `-Ttext-segment`. Debian's musl start files are compiled as
/// position-independent code, which then needs three more tricks: musl's
/// own crt1.o instead of gcc's crtbegin (which can't reach a far-away
/// `__cxa_finalize`), `--no-relax`, and a dummy `_DYNAMIC` (crt1's `_start`
/// takes its address, which is 0 -- too far away -- in a static program).
/// Static PIEs need none of this, which is why stage 19 added them.
/// Find a tool in PATH or the sbin directories (often not in a user's PATH).
/// The lines of big.txt: line i is `big.txt line {i:05}` (19 bytes with the
/// newline), so tests can check any offset. 16000 lines = 304000 bytes:
/// with 1 KiB blocks that's past the 12 direct + 256 single-indirect blocks.
pub const BIG_LINES: usize = 16000;
/// sparse.bin: 66 MiB, all holes except these 1 KiB chunks of text. With
/// 1 KiB blocks, 40 MiB is in the double-indirect range and 65 MiB in the
/// triple-indirect range (which starts at 12 + 256 + 256*256 KiB ~ 64.3 MiB).
pub const SPARSE_SIZE: u64 = 66 * 1024 * 1024;
pub const SPARSE_MARKS: & = &;
/// Copy a directory tree (files and directories only).
/// numbers.txt on the exFAT disk: 20 000 lines of 17 bytes = 340 000 bytes.
pub const NUMBER_LINES: usize = 20_000;
/// frag-chain.txt: 2 000 lines of 19 bytes = 38 000 bytes.
pub const FRAG_LINES: usize = 2_000;
// --- btrfs (stage 10) --------------------------------------------------------
/// CRC-32 (the zlib/PNG one), for the manifests. tests/btrfs.rs has its own
/// copy; scripts/btrfs-check.sh uses Python's zlib.crc32.
/// One line per path under `dir`, sorted: `D\tpath`, `F\tpath\tsize\tcrc32`
/// or `L\tpath\ttarget`. Paths are relative, with `/` separators.
/// Pseudo-random bytes (a fixed LCG, so every build makes the same file).
const BTRFS_LINES: usize = 120_000; // big.txt: 120 000 x 18 bytes = 2.16 MB
|