From owner-cvs-all@FreeBSD.ORG Wed Dec 15 00:10:35 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 646AD16A4CE; Wed, 15 Dec 2004 00:10:35 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3134543D2F; Wed, 15 Dec 2004 00:10:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 403CE51199; Tue, 14 Dec 2004 16:10:34 -0800 (PST) Date: Tue, 14 Dec 2004 16:10:34 -0800 From: Kris Kennaway To: Nate Lawson Message-ID: <20041215001034.GA60875@xor.obsecurity.org> References: <200411300618.iAU6IkQX065609@repoman.freebsd.org> <200412141333.06213.jhb@FreeBSD.org> <41BF48D4.8080305@root.org> <200412141719.10701.jhb@FreeBSD.org> <41BF6F44.2090407@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <41BF6F44.2090407@root.org> User-Agent: Mutt/1.4.2.1i cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: John Baldwin Subject: Re: cvs commit: src/sys/i386/i386 vm_machdep.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 00:10:35 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 14, 2004 at 02:55:00PM -0800, Nate Lawson wrote: > >Erm, well, that's not always easy since sometimes when you panic you can= 't=20 > >talk to the other CPUs for whatever reason. Putting back the proxy rese= t=20 > >doesn't hurt for now but does restore functionality in at least some=20 > >cases. I'd rather have that then certain hard panics not get into ddb= =20 > >because we couldn't get onto the BSP to run ddb. >=20 > Perhaps you could give me some pointers on what is counted on to be=20 > working when panic() is called? I can't come up with a situation where= =20 > the proxy code couldn't be used upon entry to ddb. If there were any=20 > cases like this, the proxy code wouldn't work for cpu_reset() either.=20 > Also, in such a case, it's hard to see how ddb could be usable since it= =20 > tries to stop other processors, which requires similar code to the proxy. >=20 > Or in other words, if you have enough capability to call panic() or=20 > break to ddb, then you have enough resources to do an IPI and get onto=20 > the BSP. NB: DDB often isn't usable on SMP machines thesedays, and will hang when a panic tries to enter it. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBv4D5Wry0BWjoQKURAp+3AJ4wzQwBNTueOPfkIP2Y0kiN+aRbhgCfW4tH qEj3YbkTMzKmLsY4W8EcEEI= =gU6p -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--