From owner-freebsd-current@FreeBSD.ORG  Fri Dec  2 10:06:01 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8E339106566B;
	Fri,  2 Dec 2011 10:06:01 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id A811B8FC08;
	Fri,  2 Dec 2011 10:06:00 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA28589;
	Fri, 02 Dec 2011 12:05:59 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
	by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1RWQ0E-000Acb-Rl; Fri, 02 Dec 2011 12:05:58 +0200
Message-ID: <4ED8A306.9020801@FreeBSD.org>
Date: Fri, 02 Dec 2011 12:05:58 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:8.0) Gecko/20111108 Thunderbird/8.0
MIME-Version: 1.0
To: John Baldwin <jhb@FreeBSD.org>
References: <20111113083215.GV50300@deviant.kiev.zoral.com.ua>
	<201112011349.50502.jhb@freebsd.org> <4ED7E6B0.30400@FreeBSD.org>
	<201112011553.34432.jhb@freebsd.org>
	<4ED7F4BC.3080206@FreeBSD.org> <4ED855E6.20207@FreeBSD.org>
In-Reply-To: <4ED855E6.20207@FreeBSD.org>
X-Enigmail-Version: undefined
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org
Subject: Re: Stop scheduler on panic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 10:06:01 -0000

on 02/12/2011 06:36 John Baldwin said the following:
> Ah, ok (I had thought SCHEDULER_STOPPED was going to always be true when kdb was
> active).  But I think these two changes should cover critical_exit() ok.
> 

I attempted to start a discussion about this a few times already :-)
Should we treat kdb context the same as SCHEDULER_STOPPED context (in the
current definition) ?  That is, skip all locks in the same fashion?
There are pros and contras.

-- 
Andriy Gapon