From: Austin Clements <austin@google.com>
Date: Thu, 9 Apr 2015 14:17:06 +0000 (-0400)
Subject: runtime: remove GoSched/GoStart trace events around GC
X-Git-Tag: go1.5beta1~1195
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=6afb5fa48fc3d33f7973fbdfeb96fdfaad51fb5f;p=gostls13.git

runtime: remove GoSched/GoStart trace events around GC

These were appropriate for STW GC, since it interrupted the allocating
Goroutine, but don't apply to concurrent GC, which runs on its own
Goroutine. Forced GC is still STW, but it makes sense to attribute the
GC to the goroutine that called runtime.GC().

Change-Id: If12418ca66dc7e53b8b16025af4e03adb5d9577e
Reviewed-on: https://go-review.googlesource.com/8715
Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Rick Hudson <rlh@golang.org>
---

diff --git a/src/runtime/mgc.go b/src/runtime/mgc.go
index e8cf95e907..8ed8c57362 100644
--- a/src/runtime/mgc.go
+++ b/src/runtime/mgc.go
@@ -324,7 +324,6 @@ func gc(mode int) {
 	}
 
 	if trace.enabled {
-		traceGoSched()
 		traceGCStart()
 	}
 
@@ -459,7 +458,6 @@ func gc(mode int) {
 
 	if trace.enabled {
 		traceGCDone()
-		traceGoStart()
 	}
 
 	// all done