aboutsummaryrefslogtreecommitdiffstats
path: root/sys/sys_amd64.const
Commit message (Collapse)AuthorAgeFilesLines
* sys: add more filesystems and mount flagsDmitry Vyukov2017-02-051-0/+8
|
* sys: minor assorted improvements to descriptionsDmitry Vyukov2017-02-031-0/+12
|
* sys: move ipc syscalls into separate fileDmitry Vyukov2017-01-281-42/+0
|
* sys: detail kvm syscalls moreDmitry Vyukov2017-01-091-0/+1
|
* sys: describe new pkey_* syscallsDmitry Vyukov2016-12-161-0/+8
|
* sys: add new bpf descriptionsDmitry Vyukov2016-11-281-0/+1
| | | | These were just added to net-next.
* sys: resolve some old TODOs in descriptionsDmitry Vyukov2016-09-051-0/+2
|
* overhaul syscall description generation processDmitry Vyukov2016-08-261-0/+840
This splits generation process into two phases: 1. Extract values of constants from linux kernel sources. 2. Generate Go code. Constant values are checked in. The advantage is that the second phase is now completely independent from linux source files, kernel version, presence of headers for particular drivers, etc. This allows to change what Go code we generate any time without access to all kernel headers (which in future won't be limited to only upstream headers). Constant extraction process does require proper kernel sources, but this can be done only once by the person who added the driver and has access to the required sources. Then the constant values are checked in for others to use. Consant extraction process is per-file/per-arch. That is, if I am adding a driver that is not present upstream and that works only on a single arch, I will check in constants only for that driver and for that arch.