From owner-svn-src-all@FreeBSD.ORG Tue Feb 10 15:13:01 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16C70D02; Tue, 10 Feb 2015 15:13:01 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0C84AE9; Tue, 10 Feb 2015 15:13:00 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YLCUe-000Hmi-11; Tue, 10 Feb 2015 18:12:52 +0300 Date: Tue, 10 Feb 2015 18:12:51 +0300 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: svn commit: r278479 - in head: etc sys/kern Message-ID: <20150210151251.GA67127@zxy.spb.ru> References: <201502092313.t19NDpoS083043@svn.freebsd.org> <1516483.e0EXgdk9ur@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" , Rui Paulo , John Baldwin X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 15:13:01 -0000 On Tue, Feb 10, 2015 at 07:06:03AM -0800, Adrian Chadd wrote: > On 10 February 2015 at 06:16, John Baldwin wrote: > > On Monday, February 09, 2015 11:13:51 PM Rui Paulo wrote: > >> Author: rpaulo > >> Date: Mon Feb 9 23:13:50 2015 > >> New Revision: 278479 > >> URL: https://svnweb.freebsd.org/changeset/base/278479 > >> > >> Log: > >> Notify devd(8) when a process crashed. > >> > >> This change implements a notification (via devctl) to userland when > >> the kernel produces coredumps after a process has crashed. > >> devd can then run a specific command to produce a human readable crash > >> report. The command is most usually a helper that runs gdb/lldb > >> commands on the file/coredump pair. It's possible to use this > >> functionality for implementing automatic generation of crash reports. > >> > >> devd(8) will be notified of the full path of the binary that crashed and > >> the full path of the coredump file. > > > > I think this is a very useful feature and I think this is fine to be in the > > tree as-is for now. My only note is that this is a bit of feature creep for > > devd (this isn't a device notification, this is a system event notification). > > As such, I think it might be worth thinking if we (collectively) want to think > > about having a separate framework at all for system event notification. You > > could possibly publish other interesting events this way. For example, Isilon > > currently has a patch to log(9) Witness LORs. I personally think it's a bit > > hackish and potentially unreliable. A much nicer interface if you want to > > capture such things would be to publish an event for each logged LOR instead. > > Machine checks are another example of something that might be nice to publish > > (though you could possibly make the case that those would not be inappropriate > > to publish via devd since actual hardware is involved). Disk and PCI errors > > are another class of thing that it would be nice to publish in an easier to > > programmaticaly parse manner. > > Cool, so someone's going to add multi-subscriber support to /dev/devctl ? > > I think devd grows these things because it's easier than teaching the > devctl interface to support multiple listeners. /dev/eventctl and eventd? And, may be, rename /dev/devctl2 to /dev/eventctl too.