From: Keith Randall <khr@golang.org>
Date: Thu, 30 Apr 2015 21:56:35 +0000 (-0700)
Subject: runtime: let freezetheworld work even when gomaxprocs=1
X-Git-Tag: go1.5beta1~750
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=5a828cfcde20c25b9b3a3387159a77eb084383b8;p=gostls13.git

runtime: let freezetheworld work even when gomaxprocs=1

Freezetheworld still has stuff to do when gomaxprocs=1.
In particular, signals can come in on other Ms (like the GC M, say)
and the single user M is still running.

Fixes #10546

Change-Id: I2f07f17d1c81e93cf905df2cb087112d436ca7e7
Reviewed-on: https://go-review.googlesource.com/9551
Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
---

diff --git a/src/runtime/proc1.go b/src/runtime/proc1.go
index 1c81b1252a..753a3a5058 100644
--- a/src/runtime/proc1.go
+++ b/src/runtime/proc1.go
@@ -216,9 +216,6 @@ const freezeStopWait = 0x7fffffff
 // There is no reverse operation, used during crashing.
 // This function must not lock any mutexes.
 func freezetheworld() {
-	if gomaxprocs == 1 {
-		return
-	}
 	// stopwait and preemption requests can be lost
 	// due to races with concurrently executing threads,
 	// so try several times