gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-11-19	Require sync.Mutex to lock and unlock from the same goroutine	Michael Pratt
	We would like to track locks ordering to detect ordering violations. Detecting violations is much simpler if mutexes must be unlocked by the same goroutine that locked them. Thus, as a first step to tracking lock ordering, add this lock/unlock requirement to gVisor's sync.Mutex. This is more strict than the Go standard library's sync.Mutex, but initial testing indicates only a single lock that is used across goroutines. The new sync.CrossGoroutineMutex relaxes the requirement (but will not provide lock order checking). Due to the additional overhead, enforcement is only enabled with the "checklocks" build tag. Build with this tag using: bazel build --define=gotags=checklocks ... From my spot-checking, this has no changed inlining properties when disabled. Updates #4804 PiperOrigin-RevId: 343370200
2020-11-12	Allow goid.Get() to be used outside of race builds.	Jamie Liu
	PiperOrigin-RevId: 342179912
2020-05-13	add arm64 support to goid	Bin Lu
	Adding a method to get g on Arm64 Signed-off-by: Bin Lu <bin.lu@arm.com>
2020-01-27	Standardize on tools directory.	Adin Scannell
	PiperOrigin-RevId: 291745021
2020-01-10	goid: new package	Ian Gudger
	Allows retrieving the goroutine ID for concurrency testing when the race detector is enabled. Updates #1472 PiperOrigin-RevId: 289155308