summary refs log tree commit diff
path: root/linux-dynamic.e
diff options
context:
space:
mode:
authorIrene Knapp <ireneista@irenes.space>2026-09-04 16:58:35 -0700
committerIrene Knapp <ireneista@irenes.space>2026-09-04 17:01:34 -0700
commit00c9a3709a2e91f847dfa19a0688204b4704034d (patch)
tree8169d1fdba136c8cf2017d74bc185e6b8dfa3549 /linux-dynamic.e
parent903cbb423e2aaf11af2e49a99b094f9600bfa25a (diff)
extensive commentary about the memory assumptions of the hex transform HEAD main
seriously there was a lot to write here. so, it's going as its own CL.

Force-Push: yes
Change-Id: I1ff091214012fb7c5f0d046f27f0b9f7b3e11ee3
Diffstat (limited to 'linux-dynamic.e')
-rw-r--r--linux-dynamic.e11
1 files changed, 8 insertions, 3 deletions
diff --git a/linux-dynamic.e b/linux-dynamic.e
index ee34e0e..3809a0e 100644
--- a/linux-dynamic.e
+++ b/linux-dynamic.e
@@ -2,9 +2,14 @@
 ~ ~~ More system calls for Linux ~~
 ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~
-~   Everything that takes a struct is here, because that lets us define the
-~ system call next to the allocation stuff, for ease of reference. There are
-~ also higher-level facilities, later in the file.
+~   Here's some more system calls for the Linux kernel, augmenting the ones in
+~ linux.e. We needed the basic I/O stuff early, to use in building the
+~ interpreter, but there's less-basic stuff that benefits from dynamic
+~ definition. That stuff is here.
+~
+~   In particular, everything that takes a struct is here, because that lets
+~ us define the system call next to the allocation stuff, for ease of
+~ reference. There are also higher-level facilities, later in the file.
 
 
 ~   Since the only way to know the struct layout is by reading the kernel