- 2012年 4月 13日 1 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 12日 23 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
These don't implement anything yet that the old syscalls didn't support, but they give us a place to pass flags and make it easier to share user code between xv6 and Linux.
-
由 Austin Clements 提交于
This fixes the syscall path so it no longer clobbers %r9, which means we can use it as the 6th function argument, following the AMD64 ABI. We still need a scratch register, but we now get that by stashing away %rax (the syscall number) in a per-CPU variable, making it available for use.
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
Bet you saw that coming.
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
It makes no sense, since it doesn't declare any avars, but is obviously capable of having physical sharing. This would only make sense if we didn't *also* declare ascopes in individual system calls.
-
由 Austin Clements 提交于
Renaming this "pte" more closely represents what's being shared. Also, previously we were inconsistent about including the vmap or not; now we use the same format everywhere.
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 10日 9 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
E.g. make RUN="avar on; ls; avar off; halt"
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
QEMU copies the command line into the bss, which makes saving it a slightly annoying process.
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 09日 3 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 08日 4 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
The only locking is "point-to-point" between condvar sleep in one proc and condvar wakeup in another.
-