mirror of
https://github.com/golang/go
synced 2024-11-23 12:10:11 -07:00
runtime: actually fix locking in BenchmarkMSpanCountAlloc
I just submitted CL 255297 which mostly fixed this problem, but totally forgot to actually acquire/release the heap lock. Oops. Updates #41391. Change-Id: I45b42f20a9fc765c4de52476db3654d4bfe9feb3 Reviewed-on: https://go-review.googlesource.com/c/go/+/255298 Trust: Michael Knyszek <mknyszek@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> Reviewed-by: Keith Randall <khr@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
This commit is contained in:
parent
37f261010f
commit
10dfb1dd3d
@ -991,7 +991,9 @@ type MSpan mspan
|
||||
func AllocMSpan() *MSpan {
|
||||
var s *mspan
|
||||
systemstack(func() {
|
||||
lock(&mheap_.lock)
|
||||
s = (*mspan)(mheap_.spanalloc.alloc())
|
||||
unlock(&mheap_.lock)
|
||||
})
|
||||
return (*MSpan)(s)
|
||||
}
|
||||
@ -999,7 +1001,9 @@ func AllocMSpan() *MSpan {
|
||||
// Free an allocated mspan.
|
||||
func FreeMSpan(s *MSpan) {
|
||||
systemstack(func() {
|
||||
lock(&mheap_.lock)
|
||||
mheap_.spanalloc.free(unsafe.Pointer(s))
|
||||
unlock(&mheap_.lock)
|
||||
})
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user