Date: Wed, 25 May 2011 17:52:13 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: mdf@FreeBSD.org Cc: Attilio Rao <attilio@FreeBSD.org>, src-committers@FreeBSD.org, Pawel Jakub Dawidek <pjd@FreeBSD.org>, svn-src-user@FreeBSD.org Subject: Re: svn commit: r222060 - in user/avg/xcpu/sys: kern sys Message-ID: <4DDD179D.5030901@FreeBSD.org> In-Reply-To: <BANLkTikmxbsCV_A-zD7XdkWyOEBzy67iZQ@mail.gmail.com> References: <201105181508.p4IF8UoS096841@svn.freebsd.org> <20110518182441.GB2273@garage.freebsd.pl> <4DD4243C.4070301@FreeBSD.org> <BANLkTikAnB-3XbvDwGHgyqyJquH9BhqzOQ@mail.gmail.com> <BANLkTikmxbsCV_A-zD7XdkWyOEBzy67iZQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 18/05/2011 23:43 mdf@FreeBSD.org said the following: > I know it's almost required now (sync on reboot?!?!), but I would > strongly question, from an architectural standpoint, why the scheduler > should be running at all in panic. Once a thread pulls the panic > trigger, nothing else should run except ddb in that thread's context. I agree, but as I've said in other email I would prefer to keep a backwards-compatibility knob for some time. Personally I don't like things like sync-on-panic, but other people may need some transition time. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDD179D.5030901>