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	-135/+0
\|
*	sys: add KVM_ENABLE_CAP for vm	Dmitry Vyukov	2017-01-18	1	-0/+3
\|
*	sys, executor: more kvm improvements	Dmitry Vyukov	2017-01-12	1	-0/+12
\| \| \| \| \| \| \|	1. Basic support for arm64 kvm testing. 2. Fix compiler warnings in x86 kvm code. 3. Test all pseudo syz calls in csource. 4. Fix handling of real code in x86.
*	sys: extend kvm support	Dmitry Vyukov	2017-01-09	1	-0/+12
\| \| \| \| \| \|	Add new pseudo syscall syz_kvm_setup_cpu that setups VCPU into interesting states for execution. KVM is too difficult to setup otherwise. Lots of improvements possible, but this is a starting point.
*	sys: detail kvm syscalls more	Dmitry Vyukov	2017-01-09	1	-5/+3
\|
*	sys: improve kvm descriptions	Dmitry Vyukov	2016-11-12	1	-0/+12
\|
*	overhaul syscall description generation process	Dmitry Vyukov	2016-08-26	1	-0/+98
	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.