syz - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	sys: move linux descriptions to sys/linux	Dmitry Vyukov	2017-09-15	1	-240/+0
\|
*	sys: reformat descriptions	Dmitry Vyukov	2017-08-18	1	-1/+0
\|
*	sys: add string flags	Dmitry Vyukov	2016-11-11	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	Allow to define string flags in txt descriptions. E.g.: filesystem = "ext2", "ext3", "ext4" and then use it in string type: ptr[in, string[filesystem]]
*	sys: specify resources in text descriptions	Dmitry Vyukov	2016-08-27	1	-95/+97
\| \| \| \| \| \|	Currently to add a new resource one needs to modify multiple source files, which complicates descirption of new system calls. Move resource descriptions from source code to text desciptions.
*	overhaul syscall description generation process	Dmitry Vyukov	2016-08-26	1	-1/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	sys: introduce a generic syz_open_dev helper syscall	Dmitry Vyukov	2016-01-13	1	-1/+1
\|
*	sys: move more subsystems into separate files	Dmitry Vyukov	2015-12-28	1	-0/+234