about summary refs log tree commit diff stats
path: root/subx/020syscalls.cc
Commit message (Collapse)AuthorAgeFilesLines
* 5471Kartik Agaram2019-07-251-4/+0
| | | | | Purge all traces of the old assumption that segment 0 is code and segment 1 is data.
* 5405Kartik Agaram2019-07-151-2/+1
|
* 5188Kartik Agaram2019-05-181-3/+2
| | | | Clean up some unused constants.
* 5157Kartik Agaram2019-05-111-9/+7
| | | | | Support allocating more than 0x01000000 bytes (8MB) to a segment in the VM.
* 5155 - check for overflow in mmap segmentsKartik Agaram2019-05-111-0/+5
|
* 5151 - use mmap everywhere we need a heapKartik Agaram2019-05-101-8/+13
| | | | | All tests passing now. Things are very explicit; before a program can `allocate` memory, it has to first obtain a segment from the OS using `new-segment`.
* 4987 - support `browse_trace` tool in SubXKartik Agaram2019-02-251-24/+24
| | | | | | | | | | | | | | | | | | I've extracted it into a separate binary, independent of my Mu prototype. I also cleaned up my tracing layer to be a little nicer. Major improvements: - Realized that incremental tracing really ought to be the default. And to minimize printing traces to screen. - Finally figured out how to combine layers and call stack frames in a single dimension of depth. The answer: optimize for the experience of `browse_trace`. Instructions occupy a range of depths based on their call stack frame, and minor details of an instruction lie one level deeper in each case. Other than that, I spent some time adjusting levels everywhere to make `browse_trace` useful.
* 4773 - done with crenshaw chapter 2-1Kartik Agaram2018-11-241-1/+0
| | | | In the process I had to fix a couple more bugs in support for disp16 instructions.
* 4695Kartik Agaram2018-10-141-2/+2
|
* 4694Kartik Agaram2018-10-131-1/+1
| | | | Check for duplicate docstrings.
* 4693Kartik Agaram2018-10-131-1/+1
| | | | | | | | Add the standard mnemonic for each opcode. We aren't ever going to have complete docs of the subset of the x86 ISA we support, so we need to help readers cross-correlate with the complete docs.
* 4665Kartik Agaram2018-10-051-11/+11
| | | | | Some syscalls expect null-terminated strings while others get lengths. Be clear about this distinction.
* 4648Kartik Agaram2018-10-011-0/+1
|
* 4619 - new syscall: mmap()Kartik Agaram2018-09-291-0/+17
|
* 4614 - redo simulated RAMKartik Agaram2018-09-291-14/+1
| | | | | | | | | | | Now simulated 'Memory' isn't just a single flat array. Instead it knows about segments and VMAs. The code segment will always be first, and the data/heap segment will always be second. The brk() syscall knows about the data segment. One nice side-effect is that I no longer need to mess with Memory initialization regardless of where I place my segments.
* 4613Kartik Agaram2018-09-291-1/+1
|
* 4552Kartik Agaram2018-09-201-6/+13
| | | | | More useful trace if we mess up args to a syscall and pass a non-pointer where a pointer is expected.
* 4522Kartik Agaram2018-08-141-3/+3
| | | | Don't use trace infrastructure if you're just going to immediately exit.
* 4520 - several syscalls for filesKartik Agaram2018-08-131-0/+78
|
* 4469Kartik Agaram2018-08-031-0/+32
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-22 09:56:36 +0000